Security readout for executives and security teams
Plain-English summary
A flaw in the Linux bnxt_en network driver can corrupt kernel memory when firmware resources change while an interface is being shut down. Successful exploitation requires local, low-privileged access, but could compromise confidentiality, integrity, and availability. Systems not using this driver are unlikely to be exposed.
Executive priority
Prioritize remediation on production, multi-tenant, or locally accessible hosts using bnxt_en. Treat other systems as inventory and verification work rather than assuming fleet-wide exposure. Because kernel memory corruption can enable full host impact, patch promptly after confirming vendor-supported packages and operational compatibility.
Technical view
During driver reinitialization, bnxt_set_dflt_rings() can under-allocate the TX ring array when multiple traffic classes exist. Later allocation in bnxt_alloc_cp_rings() can write beyond that array. The kernel fix scales TX-ring counts by bp->num_tc and introduces helpers for total and per-traffic-class ring counts.
Likely exposure
Exposure is concentrated on affected Linux kernels actively using bnxt_en, particularly where multiple traffic classes are configured and firmware resource or capability changes occur during interface shutdown. The supplied version list includes 5.4, 6.12.45, 6.16.5, and 6.17, but its range semantics are incomplete; confirm status with the kernel or distribution vendor.
Exploitation context
The CVSS vector indicates local access, low privileges, low complexity, and no user interaction. The source bundle does not establish active exploitation, public exploit availability, or inclusion in CISA KEV. Triggering also appears dependent on bnxt_en driver state, multiple traffic classes, and a firmware resource or capability change during interface shutdown.
Researcher notes
CWE-787 and CVSS 7.8 are consistent with an out-of-bounds kernel write. The vulnerable path follows firmware change flags through reinitialization and reservation cancellation into default ring-mode setup. The provided data does not map each stable commit to a specific release branch, so commit ancestry and distribution backports require vendor verification.
Mitigation direction
- Apply a vendor-supported kernel containing the referenced bnxt_en correction.
- Check Linux distribution advisories for backported fixes and exact affected package versions.
- Prioritize systems using bnxt_en with multiple traffic classes.
- Restrict local access and unnecessary privileges until patched.
- Follow vendor guidance if immediate kernel replacement is unavailable.
Validation and detection
- Inventory kernel versions and determine whether bnxt_en is loaded and actively used.
- Compare installed kernel changelogs against CVE-2025-39810 and the referenced fix commits.
- Identify systems configured with more than one traffic class.
- Confirm patched systems booted into the corrected kernel.
- Monitor affected hosts for kernel crashes or memory-corruption symptoms during interface changes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CWE-787: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2025-39810 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9LinuxCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/d00e98977ef519280b075d783653e2c492fffbb6CVE reference, Linux
- https://git.kernel.org/stable/c/9ab6a9950f152e094395d2e3967f889857daa185CVE reference, Linux
- https://git.kernel.org/stable/c/2747328ba2714f1a7454208dbbc1dc0631990b4aCVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Out-of-bounds Write
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.