Skip to main content
VulnerabilityPublished Updated

CVE-2025-40140: Linux kernel · net: usb: Remove disruptive netif_wake_queue in rtl8150_set_multicast

Source GCVE Database

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 09:08 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

A fix for this vulnerability has been implemented in the Linux kernel by removing the netif_stop_queue and netif_wake_queue calls from rtl8150_set_multicast. Users should apply the official Linux kernel updates that include this fix. Since this is a kernel-level issue, updating to the patched kernel version is the recommended remediation. Patch status is not explicitly confirmed in the provided data; therefore, check the vendor or Linux kernel advisory for the exact fixed versions and update accordingly.

Description

A high-severity vulnerability in the Linux kernel's USB network driver for the rtl8150 device was resolved. The issue involved improper synchronization in the rtl8150_set_multicast function, which incorrectly called netif_stop_queue and netif_wake_queue, leading to potential double submission of USB requests. This could cause disruptions in the transmit queue handling. The fix removes these disruptive calls, relying on the net core function dev_set_rx_mode for proper synchronization.

References

Community reviews

Loading reviews…