CVE-2025-37895 bnxt_en: Fix error handling path in bnxt_init_chip()

Medium 5.5 Published Updated

A flaw in the bnxt_en driver causes a kernel warning and potential crash when initialization fails due to improper work queue handling.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2025-37895?

CVE-2025-37895 is a medium-severity vulnerability in Linux kernel, published on 20 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

Official 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.

Which versions are affected by CVE-2025-37895?

It affects 1 product.

Products include Linux kernel.

How do I fix CVE-2025-37895?

Apply the vendor's patch.

Is CVE-2025-37895 being exploited?

There is no known exploitation of CVE-2025-37895 in the wild and no public exploit code.

All Linux kernel vulnerabilities

Sources

Also known as BELL-CVE-2025-37895, DEBIAN-CVE-2025-37895, GHSA-grfj-5cgf-q45r, UBUNTU-CVE-2025-37895.

Is CVE-2025-37895 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free