linux-cve-announce - CVE-2025-40140: net: usb: Remove disruptive netif_wake_queue in rtl8150_set

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025111255-CVE-2025-40140-ae1a@gregkh>
Date: Wed, 12 Nov 2025 19:24:16 +0900
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-40140: net: usb: Remove disruptive netif_wake_queue in rtl8150_set_multicast

From: Greg Kroah-Hartman <gregkh@...nel.org>

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.

The Linux kernel CVE team has assigned CVE-2025-40140 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 2.6.12 with commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and fixed in 5.4.301 with commit cce3c0e21cdd15bcba5c35d3af1700186de8f187
	Issue introduced in 2.6.12 with commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and fixed in 5.10.246 with commit 1a08a37ac03d07a1608a1592791041cac979fbc3
	Issue introduced in 2.6.12 with commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and fixed in 5.15.195 with commit 54f8ef1a970a8376e5846ed90854decf7c00555d
	Issue introduced in 2.6.12 with commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and fixed in 6.1.156 with commit 114e05344763a102a8844efd96ec06ba99293ccd
	Issue introduced in 2.6.12 with commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and fixed in 6.6.112 with commit 6394bade9daab8e318c165fe43bba012bf13cd8e
	Issue introduced in 2.6.12 with commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and fixed in 6.12.53 with commit 6053e47bbf212b93c051beb4261d7d5a409d0ce3
	Issue introduced in 2.6.12 with commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and fixed in 6.17.3 with commit 9d72df7f5eac946f853bf49c428c4e87a17d91da
	Issue introduced in 2.6.12 with commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and fixed in 6.18-rc1 with commit 958baf5eaee394e5fd976979b0791a875f14a179

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2025-40140
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	drivers/net/usb/rtl8150.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/cce3c0e21cdd15bcba5c35d3af1700186de8f187
	https://git.kernel.org/stable/c/1a08a37ac03d07a1608a1592791041cac979fbc3
	https://git.kernel.org/stable/c/54f8ef1a970a8376e5846ed90854decf7c00555d
	https://git.kernel.org/stable/c/114e05344763a102a8844efd96ec06ba99293ccd
	https://git.kernel.org/stable/c/6394bade9daab8e318c165fe43bba012bf13cd8e
	https://git.kernel.org/stable/c/6053e47bbf212b93c051beb4261d7d5a409d0ce3
	https://git.kernel.org/stable/c/9d72df7f5eac946f853bf49c428c4e87a17d91da
	https://git.kernel.org/stable/c/958baf5eaee394e5fd976979b0791a875f14a179