# CVE-2025-40140: net: usb: Remove disruptive netif_wake_queue in rtl8150_set_multicast

> A race condition in the rtl8150 USB network driver allows double URB submission, potentially causing a kernel warning and denial of service.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Nov 2025
- **Updated:** 5 Aug 2026
- **Also known as:** BELL-CVE-2025-40140, DEBIAN-CVE-2025-40140, GHSA-9f54-r6pv-hv3h, ROOT-OS-DEBIAN-11-CVE-2025-40140, ROOT-OS-DEBIAN-13-CVE-2025-40140, ROOT-OS-UBUNTU-2404-CVE-2025-40140, UBUNTU-CVE-2025-40140

## What is CVE-2025-40140?

CVE-2025-40140 is a high-severity vulnerability in Linux, published on 12 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2025-40140?


## How do I fix CVE-2025-40140?

Apply the vendor's patch.

## Is CVE-2025-40140 being exploited?

There is no known exploitation of CVE-2025-40140 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-40140 and fix it if it is affected.

What it is: CVE-2025-40140 is a high-severity vulnerability in Linux, published on 12 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-40140 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-40140/ (Markdown: https://insights.sbomify.com/CVE-2025-40140/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-40140
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-40140
- OSV: https://osv.dev/vulnerability/CVE-2025-40140

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-40140/
Summaries are generated and may contain mistakes; the official description above is the record.