Skip to main content
VulnerabilityPublished Updated

CVE-2025-39769: Linux kernel · bnxt_en: Fix lockdep warning during rmmod

Source GCVE Database

0
Compare

Not known to be exploited · CVSS 5.5 Medium.

Data as of 19 Nov 2026, 02:22 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 18 Nov 2026.

What to do

AI-suggested

A fix is available and has been applied in the Linux kernel source code. Users should update to the fixed kernel version once it is released. No additional mitigation is required beyond applying the official fix.

Description

CVE-2025-39769 addresses a locking assertion warning in the Linux kernel's bnxt_en network driver module during module removal (rmmod). The issue arises because a lock assertion triggers incorrectly when the network device is already unregistered. The fix involves replacing the strict lock assertion with one that allows for the unregistered state, preventing the warning and potential instability.

References

Community reviews

Loading reviews…