CVE-2026-98287

published 6 Oct 2026 · updated 12 Nov 2026

pppoatm: ensure a writable skb header and linear data

9.8CriticalCVSS 9.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 208ccc4d08b1897451e9ba01c016bf93ff107966, Kernel 30992fe39e65589ed8e000425e088fa74994b811, Kernel 8e66c5969acd859ba72fb0a7fa895623fc1b3769 and 4 more.

In the Linux kernel, the following vulnerability has been resolved: pppoatm: ensure a writable skb header and linear data In pppoatm_send(), LLC encapsulation checks whether there is sufficient headroom for the 4-byte LLC header, but does not ensure that the skb header is writable. Normal transmit packets passing through ppp_start_xmit() have their header unshared via skb_cow_head(). However, packets can also reach pppoatm_send() via PPP channel bridging (PPPIOCBRIDGECHAN) without going through ppp_start_xmit(). Use skb_cow_head() to ensure both sufficient headroom and a writable header before pushing the LLC header. While at it: - Call pskb_may_pull(skb, 1) before inspecting skb->data[0] to prevent out-of-bounds reads on zero-length or non-linear frames (e.g. from bridging). - Defer SC_COMP_PROT protocol compression until after pppoatm_may_send() succeeds. This eliminates the temporary skb allocation on admission failure and completely removes the fragile "undo" heuristic at the nospace label, avoiding any risk of reading uninitialized headroom or performing an unbalanced skb_push().

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=5.11, >=4cf476ced45d7f12df30a68e833b263e7a2202d1 <208ccc4d08b1897451e9ba01c016bf93ff107966, >=4cf476ced45d7f12df30a68e833b263e7a2202d1 <30992fe39e65589ed8e000425e088fa74994b811, >=4cf476ced45d7f12df30a68e833b263e7a2202d1 <8e66c5969acd859ba72fb0a7fa895623fc1b3769, >=4cf476ced45d7f12df30a68e833b263e7a2202d1 <e2f5529b0016db7d34f411408607f5cf395a542e, >=4cf476ced45d7f12df30a68e833b263e7a2202d1 <e6cd1bba7d113c15c00ac63671213a096fe4d686, >=4cf476ced45d7f12df30a68e833b263e7a2202d1 <ecc7253683a3c55caa868ce0ee530fcb0044bd3c, >=4cf476ced45d7f12df30a68e833b263e7a2202d1 <ffc448eb54f5ba80d4212c1e870cdb92b0f709fa208ccc4d08b1897451e9ba01c016bf93ff107966, 30992fe39e65589ed8e000425e088fa74994b811, 8e66c5969acd859ba72fb0a7fa895623fc1b3769, e2f5529b0016db7d34f411408607f5cf395a542e, e6cd1bba7d113c15c00ac63671213a096fe4d686, ecc7253683a3c55caa868ce0ee530fcb0044bd3c, ffc448eb54f5ba80d4212c1e870cdb92b0f709fa

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-98287 severity on Zeptric[![CVE-2026-98287](https://zeptric.io/badge/cve/CVE-2026-98287.svg)](https://zeptric.io/cve/CVE-2026-98287)