CVE-2025-71095: net: stmmac: fix the crash issue for zero copy XDP_TX action
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.29% (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 3f7823219407f2f18044c2b72366a48810c5c821, 45ee0462b88396a0bd1df1991f801c89994ea72b, 4d0ceb7677e1c4616afb96abb4518f70b65abb0d; azl3 kernel 6.6.119.3-3 on Azure Linux 3.0 6.6.121.1-1; cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 Release Notes.
- Severity is disputed: the assigning authority (CNA) scores it 9.1, NVD 5.5.
Low priority for now. Upgrade to Linux Linux 3f7823219407f2f18044c2b72366a48810c5c821, 45ee0462b88396a0bd1df1991f801c89994ea72b, 4d0ceb7677e1c4616afb96abb4518f70b65abb0d; azl3 kernel 6.6.119.3-3 on Azure Linux 3.0 6.6.121.1-1; cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 Release Notes 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: net: stmmac: fix the crash issue for zero copy XDP_TX action There is a crash issue when running zero copy XDP_TX action, the crash log is shown below. [ 216.122464] Unable to handle kernel paging request at virtual address fffeffff80000000 [ 216.187524] Internal error: Oops: 0000000096000144 [#1] SMP [ 216.301694] Call trace: [ 216.304130] dcache_clean_poc+0x20/0x38 (P) [ 216.308308] __dma_sync_single_for_device+0x1bc/0x1e0 [ 216.313351] stmmac_xdp_xmit_xdpf+0x354/0x400 [ 216.317701] __stmmac_xdp_run_prog+0x164/0x368 [ 216.322139] stmmac_napi_poll_rxtx+0xba8/0xf00 [ 216.326576] __napi_poll+0x40/0x218 [ 216.408054] Kernel panic - not syncing: Oops: Fatal exception in interrupt For XDP_TX action, the xdp_buff is converted to xdp_frame by xdp_convert_buff_to_frame(). The memory type of the resulting xdp_frame depends on the memory type of the xdp_buff. For page pool based xdp_buff it produces xdp_frame with memory type MEM_TYPE_PAGE_POOL. For zero copy XSK pool based xdp_buff it produces xdp_frame with memory type MEM_TYPE_PAGE_ORDER0. However, stmmac_xdp_xmit_back() does not check the memory type and always uses the page pool type, this leads to invalid mappings and causes the crash. Therefore, check the xdp_buff memory type in stmmac_xdp_xmit_back() to fix this issue.
- Published
- Jan 13, 2026
- Updated
- Nov 10, 2026
- EPSS
- 0.2% · 22th 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.2%
CNA vs NVD score
- NVD
- 5.5
- CNA · Linux
- 9.1
- 3.6 point gap
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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.13affected
- bba2556efad66e7eaa56fece13f7708caa1187f8 and later · before 3f7823219407f2f18044c2b72366a48810c5c821affected · git
- bba2556efad66e7eaa56fece13f7708caa1187f8 and later · before 4d0ceb7677e1c4616afb96abb4518f70b65abb0daffected · git
- bba2556efad66e7eaa56fece13f7708caa1187f8 and later · before 45ee0462b88396a0bd1df1991f801c89994ea72baffected · git
- bba2556efad66e7eaa56fece13f7708caa1187f8 and later · before 5e5988736a95b1de7f91b10ac2575454b70e4897affected · git
- bba2556efad66e7eaa56fece13f7708caa1187f8 and later · before a48e232210009be50591fdea8ba7c07b0f566a13affected · git
- before 5.13not affected · semver
- 6.1.160 and later · up to and including 6.1.*not affected · semver
- 6.6.120 and later · up to and including 6.6.*not affected · semver
- 6.12.64 and later · up to and including 6.12.*not affected · semver
Affected versions · NVD (6)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.13.1 and later · before 6.1.160
- linux linux kernel6.2 and later · before 6.6.120
- linux linux kernel6.7 and later · before 6.12.64
- linux linux kernel6.13 and later · before 6.18.4
- linux linux kernel5.13
- linux linux kernel6.19
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.162-1 | 6.1.162-1 |
| Debian:13 | linux | before 6.12.69-1 | 6.12.69-1 |
| Debian:14 | linux | before 6.18.5-1 | 6.18.5-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-71093Jan 13, 2026 · e1000: fix OOB in e1000_tbi_should_accept()28Monitor
- ← EarlierCVE-2025-71094Jan 13, 2026 · net: usb: asix: validate PHY address before use22Monitor
- Later →CVE-2025-71096Jan 13, 2026 · RDMA/core: Check for the presence of LS_NLA_TYPE_DGID correctly22Monitor
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 | 3f7823219407f2f18044c2b72366a48810c5c821 | Vendor (CNA) |
| Linux Linux | 45ee0462b88396a0bd1df1991f801c89994ea72b | Vendor (CNA) |
| Linux Linux | 4d0ceb7677e1c4616afb96abb4518f70b65abb0d | Vendor (CNA) |
| Linux Linux | 5e5988736a95b1de7f91b10ac2575454b70e4897 | Vendor (CNA) |
| Linux Linux | a48e232210009be50591fdea8ba7c07b0f566a13 | Vendor (CNA) |
| azl3 kernel 6.6.119.3-3 on Azure Linux 3.0 | 6.6.121.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 | Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.162-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)
—
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 (6 more)Show less
- git.kernel.org/stable/c/45ee0462b88396a0bd1df1991f801c89994ea72b
- git.kernel.org/stable/c/4d0ceb7677e1c4616afb96abb4518f70b65abb0d
- git.kernel.org/stable/c/5e5988736a95b1de7f91b10ac2575454b70e4897
- git.kernel.org/stable/c/a48e232210009be50591fdea8ba7c07b0f566a13
- cert-portal.siemens.com/productcert/html/ssa-019113.html
- cert-portal.siemens.com/productcert/html/ssa-457936.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.