CVE-2025-37895: Linux kernel · bnxt_en: Fix error handling path in bnxt_init_chip()
Affects Linux kernelSource GCVE Database
Not known to be exploited · fixed in 6.12.10 : update Linux kernel when convenient.
Data as of 5 Nov 2026, 22:03 UTC
Rated Low by Threat Radar's AI analysis · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- Patch
- Available – fixed in 6.12.10
Exploitation evidence
Disclosed: evidence found.
CVE published 20 May 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 5 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux | Affected
| Fixed in– |
AI-suggested
A fix is available in Linux kernel version 6.12.10, which sets the BNXT_STATE_NAPI_DISABLED bit during initialization to prevent the error. Users should update to this or later kernel versions to remediate the issue.
Description
A vulnerability in the Linux kernel's bnxt_en driver caused a WARN_ON() kernel warning due to improper error handling in the bnxt_init_chip() function. The issue arises because the driver attempts to cancel uninitialized dim work during error handling, triggered by the absence of the BNXT_STATE_NAPI_DISABLED bit being set during initialization. This has been fixed by setting the BNXT_STATE_NAPI_DISABLED bit during initialization to prevent canceling uninitalized work.