CVE-2025-37911 json
bnxt_en: Fix out-of-bound memcpy() during ethtool -w
published 2025-05-20 17 mo ago modified 2026-10-15 24 d ago also EUVD-2025-15943
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 15%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 4.20, 5.5, 5.15.182, 6.1.138, 6.6.90, 6.12.28, 6.14.6, 6.15
- linux Debian 12 6.1.140-1
- linux Debian 14, Debian 13 6.12.29-1
debian advisories DEBIAN-CVE-2025-37911
- linux Ubuntu 22.04 LTS 5.15.0-144.157
- linux Ubuntu 24.04 LTS 6.8.0-100.100
- linux-aws Ubuntu 22.04 LTS 5.15.0-1088.95
- linux-aws Ubuntu 24.04 LTS 6.8.0-1046.49
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1087.96
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1047.50
- linux-gke Ubuntu 22.04 LTS 5.15.0-1085.91
- linux-gke Ubuntu 24.04 LTS 6.8.0-1043.48
ubuntu advisories UBUNTU-CVE-2025-37911
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-coco SLE Module for Confidential Computing Technical Preview 15 SP6 6.4.0-15061.28.coco15sp6.1
- kernel-syms-coco SLE Module for Confidential Computing Technical Preview 15 SP6 6.4.0-15061.28.coco15sp6.1
- kernel-coco_debug SLE Module for Confidential Computing Technical Preview 15 SP6 6.4.0-15061.28.coco15sp6.1
- kernel-source-coco SLE Module for Confidential Computing Technical Preview 15 SP6 6.4.0-15061.28.coco15sp6.1
- kernel-rt Real Time Module 15 SP7 6.4.0-150700.7.8.1
- kernel-syms-rt Real Time Module 15 SP7 6.4.0-150700.7.8.1
- kernel-source-rt Real Time Module 15 SP7 6.4.0-150700.7.8.1
- kernel-64kb SLE Module for Basesystem 15 SP7 6.4.0-150700.53.6.1
suse advisories SUSE-SU-2025:02923-1SUSE-SU-2025:02334-1SUSE-SU-2025:02333-1SUSE-SU-2025:02307-1SUSE-SU-2025:02254-1SUSE-SU-2025:02000-1
- git.kernel.org/stable/c/69b10dd23ab826d0c7f2d9ab311842251978d0c1 commit
- git.kernel.org/stable/c/43292b83424158fa6ec458799f3cb9c54d18c484 commit
- git.kernel.org/stable/c/4d69864915a3a052538e4ba76cd6fd77cfc64ebe commit
- git.kernel.org/stable/c/44807af79efd0d78fa36383dd865ddfe7992c0a6 commit
- git.kernel.org/stable/c/44d81a9ebf0cad92512e0ffdf7412bfe20db66ec commit
- git.kernel.org/stable/c/6b87bd94f34370bbf1dfa59352bed8efab5bf419 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-37911 updated cvss 4.4
kernel: bnxt_en: Fix out-of-bound memcpy() during ethtool -w
-
Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 moreaffected: no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelaffected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 24 d ago
Exploit prediction
0.24% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-125 Out-of-bounds Read
- Technology feeds
References
-
git.kernel.org
/stable/c/69b10dd23ab826d0c7f2d9ab311842251978d0c1
patch
-
git.kernel.org
/stable/c/43292b83424158fa6ec458799f3cb9c54d18c484
patch
-
git.kernel.org
/stable/c/4d69864915a3a052538e4ba76cd6fd77cfc64ebe
patch
-
git.kernel.org
/stable/c/44807af79efd0d78fa36383dd865ddfe7992c0a6
patch
-
git.kernel.org
/stable/c/44d81a9ebf0cad92512e0ffdf7412bfe20db66ec
patch
-
git.kernel.org
/stable/c/6b87bd94f34370bbf1dfa59352bed8efab5bf419
patch
-
lists.debian.org
/debian-lts-announce/2025/08/msg00010.html
mailing-list
Sources
- CVE List CVE-2025-37911
- NVD CVE-2025-37911
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.