{"id":"CVE-2025-71095","title":"net: stmmac: fix the crash issue for zero copy XDP_TX action","summary":"In the Linux kernel, the following vulnerability has been resolved:\n\nnet: stmmac: fix the crash issue for zero copy XDP_TX action\n\nThere is a crash issue when running zero copy XDP_TX action, the crash\nlog is shown below.\n\n[  216.122464]…","severity":"critical","cvss":9.1,"cvssVector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H","cvssSource":"cna","vendor":"Linux","product":"Linux","affected":["Linux >= bba2556efad66e7eaa56fece13f7708caa1187f8 < 3f7823219407f2f18044c2b72366a48810c5c821","Linux >= bba2556efad66e7eaa56fece13f7708caa1187f8 < 4d0ceb7677e1c4616afb96abb4518f70b65abb0d","Linux >= bba2556efad66e7eaa56fece13f7708caa1187f8 < 45ee0462b88396a0bd1df1991f801c89994ea72b","Linux >= bba2556efad66e7eaa56fece13f7708caa1187f8 < 5e5988736a95b1de7f91b10ac2575454b70e4897","Linux >= bba2556efad66e7eaa56fece13f7708caa1187f8 < a48e232210009be50591fdea8ba7c07b0f566a13","Linux 5.13"],"published":"2026-01-13","updated":"2026-09-08","sourceUpdated":"2026-09-08T08:43:49.102Z","source":"CVEORG","sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2025-71095","references":[{"url":"https://git.kernel.org/stable/c/3f7823219407f2f18044c2b72366a48810c5c821"},{"url":"https://git.kernel.org/stable/c/4d0ceb7677e1c4616afb96abb4518f70b65abb0d"},{"url":"https://git.kernel.org/stable/c/45ee0462b88396a0bd1df1991f801c89994ea72b"},{"url":"https://git.kernel.org/stable/c/5e5988736a95b1de7f91b10ac2575454b70e4897"},{"url":"https://git.kernel.org/stable/c/a48e232210009be50591fdea8ba7c07b0f566a13"}],"tags":["cve.org"],"epss":0.0028,"epssPercentile":0.20721,"ingestedAt":"2026-09-08T15:33:26.995Z","slug":"CVE-2025-71095","body":"## Overview\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: stmmac: fix the crash issue for zero copy XDP_TX action\n\nThere is a crash issue when running zero copy XDP_TX action, the crash\nlog is shown below.\n\n[  216.122464] Unable to handle kernel paging request at virtual address fffeffff80000000\n[  216.187524] Internal error: Oops: 0000000096000144 [#1]  SMP\n[  216.301694] Call trace:\n[  216.304130]  dcache_clean_poc+0x20/0x38 (P)\n[  216.308308]  __dma_sync_single_for_device+0x1bc/0x1e0\n[  216.313351]  stmmac_xdp_xmit_xdpf+0x354/0x400\n[  216.317701]  __stmmac_xdp_run_prog+0x164/0x368\n[  216.322139]  stmmac_napi_poll_rxtx+0xba8/0xf00\n[  216.326576]  __napi_poll+0x40/0x218\n[  216.408054] Kernel panic - not syncing: Oops: Fatal exception in interrupt\n\nFor XDP_TX action, the xdp_buff is converted to xdp_frame by\nxdp_convert_buff_to_frame(). The memory type of the resulting xdp_frame\ndepends on the memory type of the xdp_buff. For page pool based xdp_buff\nit produces xdp_frame with memory type MEM_TYPE_PAGE_POOL. For zero copy\nXSK pool based xdp_buff it produces xdp_frame with memory type\nMEM_TYPE_PAGE_ORDER0. However, stmmac_xdp_xmit_back() does not check the\nmemory type and always uses the page pool type, this leads to invalid\nmappings and causes the crash. Therefore, check the xdp_buff memory type\nin stmmac_xdp_xmit_back() to fix this issue.\n\n## Affected\n\n- `Linux >= bba2556efad66e7eaa56fece13f7708caa1187f8 < 3f7823219407f2f18044c2b72366a48810c5c821`\n- `Linux >= bba2556efad66e7eaa56fece13f7708caa1187f8 < 4d0ceb7677e1c4616afb96abb4518f70b65abb0d`\n- `Linux >= bba2556efad66e7eaa56fece13f7708caa1187f8 < 45ee0462b88396a0bd1df1991f801c89994ea72b`\n- `Linux >= bba2556efad66e7eaa56fece13f7708caa1187f8 < 5e5988736a95b1de7f91b10ac2575454b70e4897`\n- `Linux >= bba2556efad66e7eaa56fece13f7708caa1187f8 < a48e232210009be50591fdea8ba7c07b0f566a13`\n- `Linux 5.13`\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"midnight","depthScore":50,"depthScoreParts":{"impact":50.1,"likelihood":0.1,"exploitation":0,"ransomware":0},"changes":[]}