CVE-2025-37911: bnxt_en: Fix out-of-bound memcpy() during ethtool -w
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 4.20, 43292b83424158fa6ec458799f3cb9c54d18c484, 44807af79efd0d78fa36383dd865ddfe7992c0a6; azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 6.6.92.2-1; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 6.6.92.2-1.
- Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 5.5.
Low priority for now. Upgrade to Linux Linux 4.20, 43292b83424158fa6ec458799f3cb9c54d18c484, 44807af79efd0d78fa36383dd865ddfe7992c0a6; azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 6.6.92.2-1; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 6.6.92.2-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: bnxt_en: Fix out-of-bound memcpy() during ethtool -w When retrieving the FW coredump using ethtool, it can sometimes cause memory corruption: BUG: KFENCE: memory corruption in __bnxt_get_coredump+0x3ef/0x670 [bnxt_en] Corrupted memory at 0x000000008f0f30e8 [ ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ] (in kfence-#45): __bnxt_get_coredump+0x3ef/0x670 [bnxt_en] ethtool_get_dump_data+0xdc/0x1a0 __dev_ethtool+0xa1e/0x1af0 dev_ethtool+0xa8/0x170 dev_ioctl+0x1b5/0x580 sock_do_ioctl+0xab/0xf0 sock_ioctl+0x1ce/0x2e0 __x64_sys_ioctl+0x87/0xc0 do_syscall_64+0x5c/0xf0 entry_SYSCALL_64_after_hwframe+0x78/0x80 ... This happens when copying the coredump segment list in bnxt_hwrm_dbg_dma_data() with the HWRM_DBG_COREDUMP_LIST FW command. The info->dest_buf buffer is allocated based on the number of coredump segments returned by the FW. The segment list is then DMA'ed by the FW and the length of the DMA is returned by FW. The driver then copies this DMA'ed segment list to info->dest_buf. In some cases, this DMA length may exceed the info->dest_buf length and cause the above BUG condition. Fix it by capping the copy length to not exceed the length of info->dest_buf. The extra DMA data contains no useful information. This code path is shared for the HWRM_DBG_COREDUMP_LIST and the HWRM_DBG_COREDUMP_RETRIEVE FW commands. The buffering is different for these 2 FW commands. To simplify the logic, we need to move the line to adjust the buffer length for HWRM_DBG_COREDUMP_RETRIEVE up, so that the new check to cap the copy length will work for both commands.
- Published
- May 20, 2025
- Updated
- Oct 15, 2026
- EPSS
- 0.2% · 15th percentile
- CWE
- CWE-125
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 5.5
- CNA · Linux
- 7.8
- 2.3 point gap
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4bf973a1f84aefb64750bdb3afe72d54de3199d7, a76837dd731b68cc3b5690470bc9efa2a8e3801a, 5.5affected
- c74751f4c39232c31214ec6a3bc1c7e62f5c728b and later · before 69b10dd23ab826d0c7f2d9ab311842251978d0c1affected · git
- c74751f4c39232c31214ec6a3bc1c7e62f5c728b and later · before 43292b83424158fa6ec458799f3cb9c54d18c484affected · git
- c74751f4c39232c31214ec6a3bc1c7e62f5c728b and later · before 4d69864915a3a052538e4ba76cd6fd77cfc64ebeaffected · git
- c74751f4c39232c31214ec6a3bc1c7e62f5c728b and later · before 44807af79efd0d78fa36383dd865ddfe7992c0a6affected · git
- c74751f4c39232c31214ec6a3bc1c7e62f5c728b and later · before 44d81a9ebf0cad92512e0ffdf7412bfe20db66ecaffected · git
- c74751f4c39232c31214ec6a3bc1c7e62f5c728b and later · before 6b87bd94f34370bbf1dfa59352bed8efab5bf419affected · git
- 4.19.95 and later · before 4.20affected · semver
- 5.4.8 and later · before 5.5affected · semver
- before 5.5not affected · semver
Affected versions · NVD (10)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux11.0
- linux linux kernel5.4.8 and later · before 5.5
- linux linux kernel5.5.1 and later · before 5.15.182
- linux linux kernel5.16 and later · before 6.1.138
- linux linux kernel6.2 and later · before 6.6.90
- linux linux kernel4.19.95 and later · before 4.20
- linux linux kernel6.13 and later · before 6.14.6
- linux linux kernel6.7 and later · before 6.12.28
- linux linux kernel5.5
- linux linux kernel6.15
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.140-1 | 6.1.140-1 |
| Debian:13 | linux | before 6.12.29-1 | 6.12.29-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-37907May 20, 2025 · accel/ivpu: Fix locking order in ivpu_job_submit22Monitor
- ← EarlierCVE-2025-37909May 20, 2025 · net: lan743x: Fix memleak issue when GSO enabled22Monitor
- Later →CVE-2025-37912May 20, 2025 · ice: Check VF VSI Pointer Value in ice_vc_add_fdir_fltr()22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 4.20 | Vendor (CNA) |
| Linux Linux | 43292b83424158fa6ec458799f3cb9c54d18c484 | Vendor (CNA) |
| Linux Linux | 44807af79efd0d78fa36383dd865ddfe7992c0a6 | Vendor (CNA) |
| Linux Linux | 44d81a9ebf0cad92512e0ffdf7412bfe20db66ec | Vendor (CNA) |
| Linux Linux | 4d69864915a3a052538e4ba76cd6fd77cfc64ebe | Vendor (CNA) |
| Linux Linux | 5.5 | Vendor (CNA) |
| Linux Linux | 69b10dd23ab826d0c7f2d9ab311842251978d0c1 | Vendor (CNA) |
| Linux Linux | 6b87bd94f34370bbf1dfa59352bed8efab5bf419 | Vendor (CNA) |
| azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 | 6.6.92.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 | 6.6.92.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.140-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/44807af79efd0d78fa36383dd865ddfe7992c0a6
- git.kernel.org/stable/c/44d81a9ebf0cad92512e0ffdf7412bfe20db66ec
- git.kernel.org/stable/c/4d69864915a3a052538e4ba76cd6fd77cfc64ebe
- git.kernel.org/stable/c/69b10dd23ab826d0c7f2d9ab311842251978d0c1
- git.kernel.org/stable/c/6b87bd94f34370bbf1dfa59352bed8efab5bf419
- lists.debian.org/debian-lts-announce/2025/08/msg00010.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.