CVE-2026-45940
Description
In the Linux kernel, the following vulnerability has been resolved: net: stmmac: fix oops when split header is enabled For GMAC4, when split header is enabled, in some rare cases, the hardware does not fill buf2 of the first descriptor with payload. Thus we cannot assume buf2 is always fully filled if it is not the last descriptor. Otherwise, the length of buf2 of the second descriptor will be calculated wrong and cause an oops: Unable to handle kernel paging request at virtual address ffff00019246bfc0 ... x2 : 0000000000000040 x1 : ffff00019246bfc0 x0 : ffff00009246c000 Call trace: dcache_inval_poc+0x28/0x58 (P) dma_direct_sync_single_for_cpu+0x38/0x6c __dma_sync_single_for_cpu+0x34/0x6c stmmac_napi_poll_rx+0x8f0/0xb60 __napi_poll.constprop.0+0x30/0x144 net_rx_action+0x160/0x274 handle_softirqs+0x1b8/0x1fc ... To fix this, the PL bit-field in RDES3 register is used for all descriptors, whether it is the last descriptor or not.
How to fix
- linux linux_kernel6.18.14, 6.19.4 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| linux linux_kernel | 5.4 ≤ v < 6.18.14, 6.19 ≤ v < 6.19.4 | 6.18.14, 6.19.4 |
| microsoft azl3_kernel_6.6.139.1-1 | No range specified | — |
| microsoft azl3_kernel_6.6.143.1-1 | No range specified | — |
| microsoft azl3_kernel_6.6.150.1-1 | No range specified | — |
| microsoft azl3_kernel_6.6.141.1-1 | No range specified | — |
| microsoft azl3_kernel_6.6.144.1-1 | No range specified | — |
| microsoft azl3_kernel_6.6.145.2-1 | No range specified | — |
| microsoft azl3_kernel_6.6.152.1-1 | No range specified | — |
| microsoft azl3_kernel_6.6.157.1-1 | No range specified | — |
| microsoft azl3_kernel_6.6.159.1-1 | No range specified | — |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.