CVE-2025-40140
Description
In the Linux kernel, the following vulnerability has been resolved:
net: usb: Remove disruptive netif_wake_queue in rtl8150_set_multicast
syzbot reported WARNING in rtl8150_start_xmit/usb_submit_urb. This is the sequence of events that leads to the warning:
rtl8150_start_xmit() { netif_stop_queue(); usb_submit_urb(dev->tx_urb); }
rtl8150_set_multicast() { netif_stop_queue(); netif_wake_queue(); <-- wakes up TX queue before URB is done }
rtl8150_start_xmit() { netif_stop_queue(); usb_submit_urb(dev->tx_urb); <-- double submission }
rtl8150_set_multicast being the ndo_set_rx_mode callback should not be calling netif_stop_queue and notif_start_queue as these handle TX queue synchronization.
The net core function dev_set_rx_mode handles the synchronization for rtl8150_set_multicast making it safe to remove these locks.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
In the Linux kernel's rtl8150 driver, a race condition in rtl8150_set_multicast can trigger a double URB submission, causing a kernel warning.
The vulnerability is a race condition in the Linux kernel's rtl8150 USB Ethernet driver. The function rtl8150_set_multicast, which is the ndo_set_rx_mode callback, improperly calls netif_stop_queue and netif_wake_queue. This disrupts the TX queue synchronization managed by the core network stack [1][2].
An attacker able to trigger the set_multicast operation while a TX is in progress can cause the TX queue to be woken prematurely. This leads to a second URB submission before the first completes, resulting in a double submission that triggers a kernel WARNING in rtl8150_start_xmit [1].
The impact is a kernel warning that can cause a denial of service (system instability or panic). No privilege escalation is described [1][2].
The fix removes the disruptive netif_wake_queue call from rtl8150_set_multicast, as the net core function dev_set_rx_mode handles synchronization properly. The fix is included in stable kernel updates [2][3].
AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
2Patches
8cce3c0e21cdd1a08a37ac03d54f8ef1a970a114e053447636394bade9daa6053e47bbf219d72df7f5eac958baf5eaee3Vulnerability mechanics
Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
8- git.kernel.org/stable/c/114e05344763a102a8844efd96ec06ba99293ccdnvd
- git.kernel.org/stable/c/1a08a37ac03d07a1608a1592791041cac979fbc3nvd
- git.kernel.org/stable/c/54f8ef1a970a8376e5846ed90854decf7c00555dnvd
- git.kernel.org/stable/c/6053e47bbf212b93c051beb4261d7d5a409d0ce3nvd
- git.kernel.org/stable/c/6394bade9daab8e318c165fe43bba012bf13cd8envd
- git.kernel.org/stable/c/958baf5eaee394e5fd976979b0791a875f14a179nvd
- git.kernel.org/stable/c/9d72df7f5eac946f853bf49c428c4e87a17d91danvd
- git.kernel.org/stable/c/cce3c0e21cdd15bcba5c35d3af1700186de8f187nvd
News mentions
0No linked articles in our index yet.