CVE-2023-54236: net/net_failover: fix txq exceeding warning
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Fixed version: Linux Linux 105cc268328231d5c2bfcbd03f265cec444a3492, 2d5cebf57296f0189a61482035ad420384eedead, 44d250c22209c680f61befbc2ac326da5452da01.
Low priority for now. Upgrade to Linux Linux 105cc268328231d5c2bfcbd03f265cec444a3492, 2d5cebf57296f0189a61482035ad420384eedead, 44d250c22209c680f61befbc2ac326da5452da01 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: net/net_failover: fix txq exceeding warning The failover txq is inited as 16 queues. when a packet is transmitted from the failover device firstly, the failover device will select the queue which is returned from the primary device if the primary device is UP and running. If the primary device txq is bigger than the default 16, it can lead to the following warning: eth0 selects TX queue 18, but real number of TX queues is 16 The warning backtrace is: [ 32.146376] CPU: 18 PID: 9134 Comm: chronyd Tainted: G E 6.2.8-1.el7.centos.x86_64 #1 [ 32.147175] Hardware name: Red Hat KVM, BIOS 1.10.2-3.el7_4.1 04/01/2014 [ 32.147730] Call Trace: [ 32.147971] <TASK> [ 32.148183] dump_stack_lvl+0x48/0x70 [ 32.148514] dump_stack+0x10/0x20 [ 32.148820] netdev_core_pick_tx+0xb1/0xe0 [ 32.149180] __dev_queue_xmit+0x529/0xcf0 [ 32.149533] ? __check_object_size.part.0+0x21c/0x2c0 [ 32.149967] ip_finish_output2+0x278/0x560 [ 32.150327] __ip_finish_output+0x1fe/0x2f0 [ 32.150690] ip_finish_output+0x2a/0xd0 [ 32.151032] ip_output+0x7a/0x110 [ 32.151337] ? __pfx_ip_finish_output+0x10/0x10 [ 32.151733] ip_local_out+0x5e/0x70 [ 32.152054] ip_send_skb+0x19/0x50 [ 32.152366] udp_send_skb.isra.0+0x163/0x3a0 [ 32.152736] udp_sendmsg+0xba8/0xec0 [ 32.153060] ? __folio_memcg_unlock+0x25/0x60 [ 32.153445] ? __pfx_ip_generic_getfrag+0x10/0x10 [ 32.153854] ? sock_has_perm+0x85/0xa0 [ 32.154190] inet_sendmsg+0x6d/0x80 [ 32.154508] ? inet_sendmsg+0x6d/0x80 [ 32.154838] sock_sendmsg+0x62/0x70 [ 32.155152] ____sys_sendmsg+0x134/0x290 [ 32.155499] ___sys_sendmsg+0x81/0xc0 [ 32.155828] ? _get_random_bytes.part.0+0x79/0x1a0 [ 32.156240] ? ip4_datagram_release_cb+0x5f/0x1e0 [ 32.156649] ? get_random_u16+0x69/0xf0 [ 32.156989] ? __fget_light+0xcf/0x110 [ 32.157326] __sys_sendmmsg+0xc4/0x210 [ 32.157657] ? __sys_connect+0xb7/0xe0 [ 32.157995] ? __audit_syscall_entry+0xce/0x140 [ 32.158388] ? syscall_trace_enter.isra.0+0x12c/0x1a0 [ 32.158820] __x64_sys_sendmmsg+0x24/0x30 [ 32.159171] do_syscall_64+0x38/0x90 [ 32.159493] entry_SYSCALL_64_after_hwframe+0x72/0xdc Fix that by reducing txq number as the non-existent primary-dev does.
- Published
- Dec 30, 2025
- Updated
- Oct 28, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.18affected
- cfc80d9a11635404a40199a1c9471c96890f3f74 and later · before 105cc268328231d5c2bfcbd03f265cec444a3492affected · git
- cfc80d9a11635404a40199a1c9471c96890f3f74 and later · before f032e125149d914e542548c17ebd613851031368affected · git
- cfc80d9a11635404a40199a1c9471c96890f3f74 and later · before 2d5cebf57296f0189a61482035ad420384eedeadaffected · git
- cfc80d9a11635404a40199a1c9471c96890f3f74 and later · before c942f5cd63b7c2e73fe06744185a34b03267595baffected · git
- cfc80d9a11635404a40199a1c9471c96890f3f74 and later · before 44d250c22209c680f61befbc2ac326da5452da01affected · git
- cfc80d9a11635404a40199a1c9471c96890f3f74 and later · before e3cbdcb0fbb61045ef3ce0e072927cc41737f787affected · git
- before 4.18not affected · semver
- 5.4.240 and later · up to and including 5.4.*not affected · semver
- 5.10.177 and later · up to and including 5.10.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.25-1 | 6.1.25-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2023-54234Dec 30, 2025 · scsi: mpi3mr: Fix missing mrioc->evtack_cmds initialization31Monitor
- ← EarlierCVE-2023-54235Dec 30, 2025 · PCI/DOE: Fix destroy_work_on_stack() race0Monitor
- Later →CVE-2023-54237Dec 30, 2025 · net/smc: fix potential panic dues to unprotected smc_llc_srv_add_link()39Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 105cc268328231d5c2bfcbd03f265cec444a3492 | Vendor (CNA) |
| Linux Linux | 2d5cebf57296f0189a61482035ad420384eedead | Vendor (CNA) |
| Linux Linux | 44d250c22209c680f61befbc2ac326da5452da01 | Vendor (CNA) |
| Linux Linux | c942f5cd63b7c2e73fe06744185a34b03267595b | Vendor (CNA) |
| Linux Linux | e3cbdcb0fbb61045ef3ce0e072927cc41737f787 | Vendor (CNA) |
| Linux Linux | f032e125149d914e542548c17ebd613851031368 | Vendor (CNA) |
| debian:linux | 6.1.25-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/2d5cebf57296f0189a61482035ad420384eedead
- git.kernel.org/stable/c/44d250c22209c680f61befbc2ac326da5452da01
- git.kernel.org/stable/c/c942f5cd63b7c2e73fe06744185a34b03267595b
- git.kernel.org/stable/c/e3cbdcb0fbb61045ef3ce0e072927cc41737f787
- git.kernel.org/stable/c/f032e125149d914e542548c17ebd613851031368
Vendor advisories and official records. Exploit/PoC links are deliberately left out.