CVE-2025-21961: eth: bnxt: fix truesize for mb-xdp-pass case
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.59% (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 01492e94a823c50f4ab5084e3ac210ba981133be, 19107e71be330dbccb9f8f9f4cf0a9abeadad802, 924ef5959b7cfbee8f923a77b0ad19b5f0a4d526.
- Severity is disputed: the assigning authority (CNA) scores it 7.5, NVD 5.5.
Low priority for now. Upgrade to Linux Linux 01492e94a823c50f4ab5084e3ac210ba981133be, 19107e71be330dbccb9f8f9f4cf0a9abeadad802, 924ef5959b7cfbee8f923a77b0ad19b5f0a4d526 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: eth: bnxt: fix truesize for mb-xdp-pass case When mb-xdp is set and return is XDP_PASS, packet is converted from xdp_buff to sk_buff with xdp_update_skb_shared_info() in bnxt_xdp_build_skb(). bnxt_xdp_build_skb() passes incorrect truesize argument to xdp_update_skb_shared_info(). The truesize is calculated as BNXT_RX_PAGE_SIZE * sinfo->nr_frags but the skb_shared_info was wiped by napi_build_skb() before. So it stores sinfo->nr_frags before bnxt_xdp_build_skb() and use it instead of getting skb_shared_info from xdp_get_shared_info_from_buff(). Splat looks like: ------------[ cut here ]------------ WARNING: CPU: 2 PID: 0 at net/core/skbuff.c:6072 skb_try_coalesce+0x504/0x590 Modules linked in: xt_nat xt_tcpudp veth af_packet xt_conntrack nft_chain_nat xt_MASQUERADE nf_conntrack_netlink xfrm_user xt_addrtype nft_coms CPU: 2 UID: 0 PID: 0 Comm: swapper/2 Not tainted 6.14.0-rc2+ #3 RIP: 0010:skb_try_coalesce+0x504/0x590 Code: 4b fd ff ff 49 8b 34 24 40 80 e6 40 0f 84 3d fd ff ff 49 8b 74 24 48 40 f6 c6 01 0f 84 2e fd ff ff 48 8d 4e ff e9 25 fd ff ff <0f> 0b e99 RSP: 0018:ffffb62c4120caa8 EFLAGS: 00010287 RAX: 0000000000000003 RBX: ffffb62c4120cb14 RCX: 0000000000000ec0 RDX: 0000000000001000 RSI: ffffa06e5d7dc000 RDI: 0000000000000003 RBP: ffffa06e5d7ddec0 R08: ffffa06e6120a800 R09: ffffa06e7a119900 R10: 0000000000002310 R11: ffffa06e5d7dcec0 R12: ffffe4360575f740 R13: ffffe43600000000 R14: 0000000000000002 R15: 0000000000000002 FS: 0000000000000000(0000) GS:ffffa0755f700000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f147b76b0f8 CR3: 00000001615d4000 CR4: 00000000007506f0 PKRU: 55555554 Call Trace: <IRQ> ? __warn+0x84/0x130 ? skb_try_coalesce+0x504/0x590 ? report_bug+0x18a/0x1a0 ? handle_bug+0x53/0x90 ? exc_invalid_op+0x14/0x70 ? asm_exc_invalid_op+0x16/0x20 ? skb_try_coalesce+0x504/0x590 inet_frag_reasm_finish+0x11f/0x2e0 ip_defrag+0x37a/0x900 ip_local_deliver+0x51/0x120 ip_sublist_rcv_finish+0x64/0x70 ip_sublist_rcv+0x179/0x210 ip_list_rcv+0xf9/0x130 How to reproduce: <Node A> ip link set $interface1 xdp obj xdp_pass.o ip link set $interface1 mtu 9000 up ip a a 10.0.0.1/24 dev $interface1 <Node B> ip link set $interfac2 mtu 9000 up ip a a 10.0.0.2/24 dev $interface2 ping 10.0.0.1 -s 65000 Following ping.py patch adds xdp-mb-pass case. so ping.py is going to be able to reproduce this issue.
- Published
- Apr 1, 2025
- Updated
- Oct 30, 2026
- EPSS
- 0.5% · 48th percentile
- CWE
- —
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.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 5.5
- CNA · Linux
- 7.5
- 2.0 point gap
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 |
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
- 5.19affected
- 1dc4c557bfedfcdf7fc0c46795857773b7ad66e7 and later · before 01492e94a823c50f4ab5084e3ac210ba981133beaffected · git
- 1dc4c557bfedfcdf7fc0c46795857773b7ad66e7 and later · before 924ef5959b7cfbee8f923a77b0ad19b5f0a4d526affected · git
- 1dc4c557bfedfcdf7fc0c46795857773b7ad66e7 and later · before 19107e71be330dbccb9f8f9f4cf0a9abeadad802affected · git
- 1dc4c557bfedfcdf7fc0c46795857773b7ad66e7 and later · before b4679807c6083ade4d47f03f80da891afcb6ef62affected · git
- 1dc4c557bfedfcdf7fc0c46795857773b7ad66e7 and later · before 9f7b2aa5034e24d3c49db73d5f760c0435fe31c2affected · git
- before 5.19not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.160 and later · up to and including 6.6.*not affected · semver
- 6.12.20 and later · up to and including 6.12.*not affected · semver
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.19 and later · before 6.12.20
- linux linux kernel6.13 and later · before 6.13.8
- linux linux kernel6.14
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | kernel-abi-stablelists | before 6.12.0-55.19.1.el10_0 | 6.12.0-55.19.1.el10_0 |
| AlmaLinux:10 | kernel-doc | before 6.12.0-55.19.1.el10_0 | 6.12.0-55.19.1.el10_0 |
| AlmaLinux:9 | kernel | before 5.14.0-570.22.1.el9_6 | 5.14.0-570.22.1.el9_6 |
| AlmaLinux:9 | kernel-64k | before 5.14.0-570.22.1.el9_6 | 5.14.0-570.22.1.el9_6 |
| AlmaLinux:9 | kernel-64k-core | before 5.14.0-570.22.1.el9_6 | 5.14.0-570.22.1.el9_6 |
| AlmaLinux:9 | kernel-64k-debug | before 5.14.0-570.22.1.el9_6 | 5.14.0-570.22.1.el9_6 |
| AlmaLinux:9 | kernel-64k-debug-core | before 5.14.0-570.22.1.el9_6 | 5.14.0-570.22.1.el9_6 |
| AlmaLinux:9 | kernel-64k-debug-devel | before 5.14.0-570.22.1.el9_6 | 5.14.0-570.22.1.el9_6 |
| AlmaLinux:9 | kernel-64k-debug-devel-matched | before 5.14.0-570.22.1.el9_6 | 5.14.0-570.22.1.el9_6 |
| AlmaLinux:9 | kernel-64k-debug-modules | before 5.14.0-570.22.1.el9_6 | 5.14.0-570.22.1.el9_6 |
| AlmaLinux:9 | kernel-64k-debug-modules-core | before 5.14.0-570.22.1.el9_6 | 5.14.0-570.22.1.el9_6 |
| AlmaLinux:9 | kernel-64k-debug-modules-extra | before 5.14.0-570.22.1.el9_6 | 5.14.0-570.22.1.el9_6 |
| AlmaLinux:9 | kernel-64k-devel | before 5.14.0-570.22.1.el9_6 | 5.14.0-570.22.1.el9_6 |
| AlmaLinux:9 | kernel-64k-devel-matched | before 5.14.0-570.22.1.el9_6 | 5.14.0-570.22.1.el9_6 |
| AlmaLinux:9 | kernel-64k-modules | before 5.14.0-570.22.1.el9_6 | 5.14.0-570.22.1.el9_6 |
| AlmaLinux:9 | kernel-64k-modules-core | before 5.14.0-570.22.1.el9_6 | 5.14.0-570.22.1.el9_6 |
| AlmaLinux:9 | kernel-64k-modules-extra | before 5.14.0-570.22.1.el9_6 | 5.14.0-570.22.1.el9_6 |
| AlmaLinux:9 | kernel-abi-stablelists | before 5.14.0-570.22.1.el9_6 | 5.14.0-570.22.1.el9_6 |
| AlmaLinux:9 | kernel-core | before 5.14.0-570.22.1.el9_6 | 5.14.0-570.22.1.el9_6 |
| AlmaLinux:9 | kernel-cross-headers | before 5.14.0-570.22.1.el9_6 | 5.14.0-570.22.1.el9_6 |
| AlmaLinux:9 | kernel-debug | before 5.14.0-570.22.1.el9_6 | 5.14.0-570.22.1.el9_6 |
| AlmaLinux:9 | kernel-debug-core | before 5.14.0-570.22.1.el9_6 | 5.14.0-570.22.1.el9_6 |
| AlmaLinux:9 | kernel-debug-devel | before 5.14.0-570.22.1.el9_6 | 5.14.0-570.22.1.el9_6 |
| AlmaLinux:9 | kernel-debug-devel-matched | before 5.14.0-570.22.1.el9_6 | 5.14.0-570.22.1.el9_6 |
+96
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-21955Apr 1, 2025 · ksmbd: prevent connection release during oplock break notification22Monitor
- ← EarlierCVE-2025-21959Apr 1, 2025 · netfilter: nf_conncount: Fully initialize struct nf_conncount_tuple in insert_tree()22Monitor
- Later →CVE-2025-21967Apr 1, 2025 · ksmbd: fix use-after-free in ksmbd_free_work_struct31Monitor
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 | 01492e94a823c50f4ab5084e3ac210ba981133be | Vendor (CNA) |
| Linux Linux | 19107e71be330dbccb9f8f9f4cf0a9abeadad802 | Vendor (CNA) |
| Linux Linux | 924ef5959b7cfbee8f923a77b0ad19b5f0a4d526 | Vendor (CNA) |
| Linux Linux | 9f7b2aa5034e24d3c49db73d5f760c0435fe31c2 | Vendor (CNA) |
| Linux Linux | b4679807c6083ade4d47f03f80da891afcb6ef62 | Vendor (CNA) |
| almalinux:kernel | 5.14.0-570.22.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k | 5.14.0-570.22.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-core | 5.14.0-570.22.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 5.14.0-570.22.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 5.14.0-570.22.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 5.14.0-570.22.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 5.14.0-570.22.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 5.14.0-570.22.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 5.14.0-570.22.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 5.14.0-570.22.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 5.14.0-570.22.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel-matched | 5.14.0-570.22.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| debian:linux | 6.1.192-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.20-1 · Debian:13 | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-570.22.1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-570.22.1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-570.22.1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-570.22.1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-570.22.1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-570.22.1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-570.22.1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-570.22.1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-570.22.1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:5.14.0-570.22.1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:5.14.0-570.22.1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
+1
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)
—
CVSS 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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.