CVE-2026-43180: net: usb: kaweth: remove TX queue manipulation in kaweth_set_rx_mode
In the Linux kernel, the following vulnerability has been resolved:
net: usb: kaweth: remove TX queue manipulation in kaweth_set_rx_mode
kaweth_set_rx_mode(), the ndo_set_rx_mode callback, calls
netif_stop_queue() and netif_wake_queue(). These are TX queue flow
control functions unrelated to RX multicast configuration.
The premature netif_wake_queue() can re-enable TX while tx_urb is still
in-flight, leading to a double usb_submit_urb() on the same URB:
kaweth_start_xmit() {
netif_stop_queue();
usb_submit_urb(kaweth->tx_urb);
}
kaweth_set_rx_mode() {
netif_stop_queue();
netif_wake_queue(); // wakes TX queue before URB is done
}
kaweth_start_xmit() {
netif_stop_queue();
usb_submit_urb(kaweth->tx_urb); // URB submitted while active
}
This triggers the WARN in usb_submit_urb():
"URB submitted while active"
This is a similar class of bug fixed in rtl8150 by
- commit 958baf5eaee3 ("net: usb: Remove disruptive netif_wake_queue in rtl8150_set_multicast").
Also kaweth_set_rx_mode() is already functionally broken, the
real set_rx_mode action is performed by kaweth_async_set_rx_mode(),
which in turn is not a no-op only at ndo_open() time.
Security readout for executives and security teams
Plain-English summary
A flaw in the Linux kaweth USB Ethernet driver can incorrectly restart network transmission while a USB transfer is still active. A local, low-privileged user may trigger conflicting submissions of the same transfer object. The documented immediate result is a kernel warning; the supplied CVSS assessment indicates potentially serious confidentiality, integrity, and availability consequences, but those outcomes are not demonstrated in the bundle.
Executive priority
Treat as a high-priority, targeted kernel update rather than an internet-wide emergency. Patch exposed multi-user systems promptly, especially those using kaweth-based USB networking. Broader fleets should first verify driver usage and vendor package status. There is no supplied evidence of active exploitation or remote attackability.
Technical view
kaweth_set_rx_mode() improperly calls transmit-queue control functions during receive-mode configuration. Its premature netif_wake_queue() can let kaweth_start_xmit() submit tx_urb again before the prior submission completes, producing an “URB submitted while active” warning. Stable-kernel fixes remove this TX queue manipulation. The supplied vector is CVSS 3.1 7.8: local, low complexity, low privileges, and no user interaction.
Likely exposure
Exposure is limited to Linux systems running an affected kernel where the kaweth USB Ethernet driver is present and exercised. Systems without this driver or relevant hardware usage are unlikely to reach the vulnerable path. The supplied version data spans numerous kernel lines, but exact distribution-package status must be confirmed with each vendor.
Exploitation context
The supplied record does not identify public exploitation, proof-of-concept availability, or CISA KEV listing. Exploitation is characterized as local and requiring low privileges. The documented trigger reaches a USB-core warning through a duplicate active-URB submission; reliable security impact beyond that warning is not established by the provided evidence.
Researcher notes
The vulnerable behavior is a race-like queue-state error between receive-mode configuration and transmit completion. The fix removes unrelated netif_stop_queue() and netif_wake_queue() calls from kaweth_set_rx_mode(). The bundle notes that actual receive-mode work occurs in kaweth_async_set_rx_mode(), mainly during ndo_open(). No CWE classification or demonstrated exploitation primitive is supplied.
Mitigation direction
Upgrade to a vendor-supported kernel containing the applicable stable-kernel fix.
Check distribution advisories for the corrected package version on each deployed kernel branch.
Where operationally acceptable, avoid using the kaweth driver until patched.
Prioritize shared or multi-user systems where untrusted local users can exercise the affected interface.
Validation and detection
Inventory kernel versions and identify systems loading or using the kaweth driver.
Map installed distribution packages to vendor advisories or the referenced stable fixes.
After upgrading, confirm systems booted into the corrected kernel.
Review kernel logs for active-URB submission warnings associated with kaweth activity.
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-2026-43180 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
1CVSS vectors
3Timeline events
0ADP providers
9Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.