ppp_synctty: ensure a writeable skb header
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 4cf476ced45d7f12df30a68e833b263e7a2202d1 · < 15d0a6c9a42df2d745c37510dba828f6dbe60d9f| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ppp_synctty: ensure a writeable skb header
ppp_sync_txmunge() checks headroom before prepending the address and control bytes, but does not ensure that the skb header is writable. A received skb can reach this function through PPP channel bridging without passing through ppp_start_xmit(), which calls skb_cow_head().
For example, a PPPoE frame may share its buffer with a clone queued to an AF_PACKET socket. If it is bridged to a synchronous tty channel, the address/control bytes can overwrite data still visible to that socket.
Use skb_cow_head() to ensure both sufficient headroom and a writable header.
From the CVE record · Linux
The Linux kernel’s ppp_synctty code checks for header space before prepending bytes but does not ensure the header is writable. When a received packet is bridged to a synchronous tty PPP channel, it can overwrite data still visible to another user of a shared buffer; the input does not specify authentication or user-interaction requirements.
Operators running the Linux kernel with PPP channel bridging to a synchronous tty channel should check their kernel; affected versions are not specified.