CVE-2026-98287

Unknown

Description

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().

SeverityUnknown
CVSS—
Exploit probability—
ProductLinux
PublishedOct 6, 2026
First seenOct 6, 2026

How to fix

Update
  • Linux Linux208ccc4d08b1897451e9ba01c016bf93ff107966, e6cd1bba7d113c15c00ac63671213a096fe4d686, ffc448eb54f5ba80d4212c1e870cdb92b0f709fa, 8e66c5969acd859ba72fb0a7fa895623fc1b3769, e2f5529b0016db7d34f411408607f5cf395a542e, 30992fe39e65589ed8e000425e088fa74994b811, ecc7253683a3c55caa868ce0ee530fcb0044bd3c or later

Affected products

ProductAffected versionsFixed in
Linux Linux4cf476ced45d7f12df30a68e833b263e7a2202d1 ≤ v < 208ccc4d08b1897451e9ba01c016bf93ff107966, 4cf476ced45d7f12df30a68e833b263e7a2202d1 ≤ v < e6cd1bba7d113c15c00ac63671213a096fe4d686, 4cf476ced45d7f12df30a68e833b263e7a2202d1 ≤ v < ffc448eb54f5ba80d4212c1e870cdb92b0f709fa, 4cf476ced45d7f12df30a68e833b263e7a2202d1 ≤ v < 8e66c5969acd859ba72fb0a7fa895623fc1b3769, 4cf476ced45d7f12df30a68e833b263e7a2202d1 ≤ v < e2f5529b0016db7d34f411408607f5cf395a542e, 4cf476ced45d7f12df30a68e833b263e7a2202d1 ≤ v < 30992fe39e65589ed8e000425e088fa74994b811, 4cf476ced45d7f12df30a68e833b263e7a2202d1 ≤ v < ecc7253683a3c55caa868ce0ee530fcb0044bd3c, 5.11208ccc4d08b1897451e9ba01c016bf93ff107966, e6cd1bba7d113c15c00ac63671213a096fe4d686, ffc448eb54f5ba80d4212c1e870cdb92b0f709fa, 8e66c5969acd859ba72fb0a7fa895623fc1b3769, e2f5529b0016db7d34f411408607f5cf395a542e, 30992fe39e65589ed8e000425e088fa74994b811, ecc7253683a3c55caa868ce0ee530fcb0044bd3c

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.