LiveActive security incident?Get immediate response
CVE Record

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

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel driver reliability flaw in bnxt_en. If chip initialization fails, the driver can trigger a kernel warning by trying to cancel work that was never initialized. The provided sources do not show remote exploitation, privilege escalation, data theft, or a public exploit.

Executive priority

Treat this as a targeted Linux kernel maintenance item, not an emergency based on current evidence. Patch during the next appropriate kernel update window, faster for critical systems using bnxt_en network interfaces.

Technical view

bnxt_init_chip() error handling may call cancel_work_sync() on uninitialized DIM work because BNXT_STATE_NAPI_DISABLED is not set in the bnxt_open() path. The kernel fix sets BNXT_STATE_NAPI_DISABLED during initialization, then clears it when NAPI and DIM work are initialized.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions where the bnxt_en network driver is present and used. The source bundle lists affected Linux versions and kernel stable commits, but gives no distro-specific package names or deployment prevalence.

Exploitation context

The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation. The evidence describes a driver error-handling warning, not a confirmed attacker-driven exploitation path.

Researcher notes

Evidence is narrow and kernel-specific. The source bundle provides the root cause and fix direction, but no CVSS, CWE, exploitability analysis, distro matrix, or proof of active exploitation. Validate exposure through actual driver use, not kernel version alone.

Mitigation direction

  • Update to a kernel or vendor package containing the referenced bnxt_en stable fixes.
  • Check Linux distribution advisories for backported fixes matching CVE-2025-37895.
  • Prioritize hosts that load the bnxt_en driver in production network paths.
  • Avoid direct wrangler or deployment assumptions; follow normal kernel change controls.

Validation and detection

  • Inventory kernel versions against the affected and fixed versions in vendor advisories.
  • Confirm whether the bnxt_en module is loaded or built into running kernels.
  • Review kernel logs for WARN_ON traces involving __flush_work() and bnxt_init_chip().
  • Verify installed kernel changelogs include CVE-2025-37895 or the referenced stable commits.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-37895 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxf697217f980ffc796c72c34dbf7d59a6b1996888, 40452969a50652e3cbf89dac83d54eebf2206d27, 40452969a50652e3cbf89dac83d54eebf2206d27, 6.12.10unaffected
LinuxLinux6.13, 0, 6.12.28, 6.14.6, 6.15affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.