pppoatm: ensure a writable skb header and linear data
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.15.222, 6.1.189, 6.6.158, 6.12.112, 6.18.54, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 4cf476ced45d7f12df30a68e833b263e7a2202d1 · fixed in 208ccc4d08b1897451e9ba01c016bf93ff107966; From 4cf476ced45d7f12df30a68e833b263e7a2202d1 · fixed in e6cd1bba7d113c15c00ac63671213a096fe4d686; From 4cf476ced45d7f12df30a68e833b263e7a2202d1 · fixed in ffc448eb54f5ba80d4212c1e870cdb92b0f709fa; From 4cf476ced45d7f12df30a68e833b263e7a2202d1 · fixed in 8e66c5969acd859ba72fb0a7fa895623fc1b3769; From 4cf476ced45d7f12df30a68e833b263e7a2202d1 · fixed in e2f5529b0016db7d34f411408607f5cf395a542e; From 4cf476ced45d7f12df30a68e833b263e7a2202d1 · fixed in 30992fe39e65589ed8e000425e088fa74994b811; From 4cf476ced45d7f12df30a68e833b263e7a2202d1 · fixed in ecc7253683a3c55caa868ce0ee530fcb0044bd3c
- Linux Linux
5.11
- KernelLinux
From 5.11.0 · fixed in 5.15.222; From 5.16.0 · fixed in 6.1.189; From 6.2.0 · fixed in 6.6.158; From 6.7.0 · fixed in 6.12.112; From 6.13.0 · fixed in 6.18.54; From 6.19.0 · fixed in 7.2.8
References 7
git.kernel.org
- stable/c/208ccc4d08b1897451e9ba01c016bf93ff107966
- stable/c/e6cd1bba7d113c15c00ac63671213a096fe4d686
- stable/c/ffc448eb54f5ba80d4212c1e870cdb92b0f709fa
- stable/c/8e66c5969acd859ba72fb0a7fa895623fc1b3769
- stable/c/e2f5529b0016db7d34f411408607f5cf395a542e
- stable/c/30992fe39e65589ed8e000425e088fa74994b811
- stable/c/ecc7253683a3c55caa868ce0ee530fcb0044bd3c