net: stmmac: fix the crash issue for zero copy XDP_TX action
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel a48e232210009be50591fdea8ba7c07b0f566a13, Kernel 6.18.4, Kernel 6.6.120 and 6 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=bba2556efad66e7eaa56fece13f7708caa1187f8 <a48e232210009be50591fdea8ba7c07b0f566a13, >=6.13 <6.18.4, >=6.2 <6.6.120, >=6.7 <6.12.64, =5.13, =6.19, >=bba2556efad66e7eaa56fece13f7708caa1187f8 <45ee0462b88396a0bd1df1991f801c89994ea72b, >=bba2556efad66e7eaa56fece13f7708caa1187f8 <4d0ceb7677e1c4616afb96abb4518f70b65abb0d, >=bba2556efad66e7eaa56fece13f7708caa1187f8 <5e5988736a95b1de7f91b10ac2575454b70e4897, >=5.13.1 <6.1.160, >=bba2556efad66e7eaa56fece13f7708caa1187f8 <3f7823219407f2f18044c2b72366a48810c5c821 | a48e232210009be50591fdea8ba7c07b0f566a13, 6.18.4, 6.6.120, 6.12.64, 45ee0462b88396a0bd1df1991f801c89994ea72b, 4d0ceb7677e1c4616afb96abb4518f70b65abb0d, 5e5988736a95b1de7f91b10ac2575454b70e4897, 6.1.160, 3f7823219407f2f18044c2b72366a48810c5c821 |
| linux-kernel: Kernel | >=5.13.0 <6.1.160, >=6.13.0 <6.18.4, >=6.2.0 <6.6.120, >=6.7.0 <6.12.64 | 6.1.160, 6.18.4, 6.6.120, 6.12.64 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket