CVE-2025-37895
MediumIn 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 3.1 score
5.5
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected versions
Linux kernel versions
6.12.10,
6.13
and later are affected. Fixed in
6.12.28,
6.14.6,
6.15
and their respective stable series.
References
3 totalFrequently asked questions
-
What is CVE-2025-37895?
CVE-2025-37895 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10 . It affects Linux kernel versions from 6.12.10 onward and has been patched in 6.12.28, 6.14.6 and 6.15. CVE-2025-37895 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
What is the CVSS score for CVE-2025-37895?
CVE-2025-37895 has a CVSS score of 5.5 out of 10, rated Medium severity (CVSS 3.1). The vector string is
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H. -
Is there a patch available for CVE-2025-37895?
Yes. CVE-2025-37895 has been patched. Fixed versions include 6.12.28, 6.14.6 and 6.15. If you are running Linux kernel 6.12.10 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2025-37895 actively exploited?
No. CVE-2025-37895 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.