CVE-2026-98287pppoatm: ensure a writable skb header and linear data
- —Not scoredno CVSS score yet
- 0.17%Exploitation in 30 daysEPSS · top 93% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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().
Timeline
ID reserved
By Linux
- 11 days later
· 11 days later
Published
- 13 days later
· 13 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.17% · top 93% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 4cf476ced45d7f12df30a68e833b263e7a2202d1 – < 208ccc4d08b1897451e9ba01c016bf93ff107966
- affected 4cf476ced45d7f12df30a68e833b263e7a2202d1 – < e6cd1bba7d113c15c00ac63671213a096fe4d686
- affected 4cf476ced45d7f12df30a68e833b263e7a2202d1 – < ffc448eb54f5ba80d4212c1e870cdb92b0f709fa
- affected 4cf476ced45d7f12df30a68e833b263e7a2202d1 – < 8e66c5969acd859ba72fb0a7fa895623fc1b3769
- affected 4cf476ced45d7f12df30a68e833b263e7a2202d1 – < e2f5529b0016db7d34f411408607f5cf395a542e
- affected 4cf476ced45d7f12df30a68e833b263e7a2202d1 – < 30992fe39e65589ed8e000425e088fa74994b811
- affected 4cf476ced45d7f12df30a68e833b263e7a2202d1 – < ecc7253683a3c55caa868ce0ee530fcb0044bd3c
- affected 5.11
- unaffected < 5.11
- unaffected 5.15.222 – ≤ 5.15.*
- unaffected 6.1.189 – ≤ 6.1.*
- unaffected 6.6.158 – ≤ 6.6.*
- unaffected 6.12.112 – ≤ 6.12.*
- unaffected 6.18.54 – ≤ 6.18.*
- unaffected 7.2.8 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References7
- https://git.kernel.org/stable/c/208ccc4d08b1897451e9ba01c016bf93ff107966 (opens in a new tab)
- https://git.kernel.org/stable/c/e6cd1bba7d113c15c00ac63671213a096fe4d686 (opens in a new tab)
- https://git.kernel.org/stable/c/ffc448eb54f5ba80d4212c1e870cdb92b0f709fa (opens in a new tab)
- https://git.kernel.org/stable/c/8e66c5969acd859ba72fb0a7fa895623fc1b3769 (opens in a new tab)
- https://git.kernel.org/stable/c/e2f5529b0016db7d34f411408607f5cf395a542e (opens in a new tab)
- https://git.kernel.org/stable/c/30992fe39e65589ed8e000425e088fa74994b811 (opens in a new tab)
- https://git.kernel.org/stable/c/ecc7253683a3c55caa868ce0ee530fcb0044bd3c (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-93215 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-98287)Record last updated .