LiveActive security incident?Get immediate response
CVE Record

CVE-2023-54236: net/net_failover: fix txq exceeding warning

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel networking flaw in net_failover. In certain failover setups, the failover interface can choose a transmit queue number that does not exist on the failover device, causing a kernel warning and stack trace. The public sources do not show active exploitation or a defined business impact beyond the kernel warning behavior.

Executive priority

Treat as a targeted Linux maintenance issue, not an emergency, unless affected failover hosts are business-critical or warnings destabilize operations. The absence of CVSS, KEV listing, and exploitation evidence keeps urgency uncertain.

Technical view

net_failover initializes the failover device with 16 transmit queues. If the primary device is up and has more transmit queues, the failover path may select a queue above 15, triggering a warning such as selecting TX queue 18 when only 16 exist. Stable kernel commits adjust the failover queue count handling.

Likely exposure

Exposure appears limited to Linux systems using net_failover, especially where the primary network device has more transmit queues than the failover device default. The bundle lists Linux kernel versions and stable commits but does not provide distribution package names or complete environment prerequisites.

Exploitation context

No cited source reports active exploitation, and KEV is false. The available evidence describes a kernel warning/backtrace during packet transmission through a failover device. The bundle does not establish remote exploitability, privilege requirements, or confidentiality/integrity impact.

Researcher notes

The record lacks CVSS, CWE, and exploitability detail. Analysis should focus on net_failover queue selection behavior, affected kernel lineage, and whether downstream vendors backported the listed stable commits. Avoid assuming broader impact without vendor confirmation.

Mitigation direction

  • Identify Linux hosts using net_failover or failover network devices.
  • Update to a vendor kernel containing the referenced stable fixes.
  • Check Linux distribution advisories for exact fixed package versions.
  • Prioritize systems where kernel warnings affect availability monitoring.
  • Monitor logs for TX queue warning messages on failover interfaces.

Validation and detection

  • Confirm the running kernel includes an applicable stable fix commit.
  • Inventory failover interfaces and associated primary device TX queue counts.
  • Review kernel logs for netdev TX queue warning backtraces.
  • Verify distribution security advisories map this CVE to installed packages.
Prepared
Confidence
medium
Sources
8

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-54236 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
7Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxcfc80d9a11635404a40199a1c9471c96890f3f74, cfc80d9a11635404a40199a1c9471c96890f3f74, cfc80d9a11635404a40199a1c9471c96890f3f74, cfc80d9a11635404a40199a1c9471c96890f3f74, cfc80d9a11635404a40199a1c9471c96890f3f74, cfc80d9a11635404a40199a1c9471c96890f3f74unaffected
LinuxLinux4.18, 0, 5.4.240, 5.10.177, 5.15.106, 6.1.23, 6.2.10, 6.3affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.