Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: bnxt_en: Fix error handling path in bnxt_init_chip() WARN_ON() is triggered in __flush_work() if bnxt_init_chip() fails because we call cancel_work_sync() on dim work that has not been initialized. WARNING: CPU: 37 PID: 5223 at kernel/workqueue.c:4201 __flush_work.isra.0+0x212/0x230 The driver relies on the BNXT_STATE_NAPI_DISABLED bit to check if dim work has already been cancelled. But in the bnxt_open() path, BNXT_STATE_NAPI_DISABLED is not set and this causes the error path to think that it needs to cancel the uninitalized dim work. Fix it by setting BNXT_STATE_NAPI_DISABLED during initialization. The bit will be cleared when we enable NAPI and initialize dim work.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 6.12.10, < 6.12.28 |
References
- https://git.kernel.org/stable/c/21116727f452474502ee74f956d5e7466103e19bPatch
- https://git.kernel.org/stable/c/9ab7a709c926c16b4433cf02d04fcbcf35aaab2bPatch
- https://git.kernel.org/stable/c/e039b00ddbfeaa0dc59b8659be114f1a1b37c5bfPatch
FAQ
What is CVE-2025-37895?
CVE-2025-37895 is a vulnerability with a CVSS score of 5.5 (MEDIUM). In the Linux kernel, the following vulnerability has been resolved: bnxt_en: Fix error handling path in bnxt_init_chip() WARN_ON() is triggered in __flush_work() if bnxt_init_chip() fails because we...
How severe is CVE-2025-37895?
CVE-2025-37895 has been rated MEDIUM with a CVSS base score of 5.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2025-37895?
Check the references section above for vendor advisories and patch information. Affected products include: Linux Linux Kernel.