CVE-2025-71095

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net: stmmac: fix the crash issue for zero copy XDP_TX action<br /> <br /> There is a crash issue when running zero copy XDP_TX action, the crash<br /> log is shown below.<br /> <br /> [ 216.122464] Unable to handle kernel paging request at virtual address fffeffff80000000<br /> [ 216.187524] Internal error: Oops: 0000000096000144 [#1] SMP<br /> [ 216.301694] Call trace:<br /> [ 216.304130] dcache_clean_poc+0x20/0x38 (P)<br /> [ 216.308308] __dma_sync_single_for_device+0x1bc/0x1e0<br /> [ 216.313351] stmmac_xdp_xmit_xdpf+0x354/0x400<br /> [ 216.317701] __stmmac_xdp_run_prog+0x164/0x368<br /> [ 216.322139] stmmac_napi_poll_rxtx+0xba8/0xf00<br /> [ 216.326576] __napi_poll+0x40/0x218<br /> [ 216.408054] Kernel panic - not syncing: Oops: Fatal exception in interrupt<br /> <br /> For XDP_TX action, the xdp_buff is converted to xdp_frame by<br /> xdp_convert_buff_to_frame(). The memory type of the resulting xdp_frame<br /> depends on the memory type of the xdp_buff. For page pool based xdp_buff<br /> it produces xdp_frame with memory type MEM_TYPE_PAGE_POOL. For zero copy<br /> XSK pool based xdp_buff it produces xdp_frame with memory type<br /> MEM_TYPE_PAGE_ORDER0. However, stmmac_xdp_xmit_back() does not check the<br /> memory type and always uses the page pool type, this leads to invalid<br /> mappings and causes the crash. Therefore, check the xdp_buff memory type<br /> in stmmac_xdp_xmit_back() to fix this issue.