pppoe: reload header pointer after dev_hard_header()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · < 6866abf59976d273164a6624234d96a967280223| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
pppoe: reload header pointer after dev_hard_header()
pppoe_sendmsg() saves a pointer to the PPPoE header before calling dev_hard_header(). Device header callbacks are allowed to reallocate the skb head, invalidating pointers into it.
This can happen when a send is blocked in copy_from_user() while the first non-Ethernet port is added to an empty team device. The team's delegated GRE header callback then expands the skb head. PPPoE subsequently writes six bytes through the stale pointer into the freed head.
Reload the PPPoE header through the skb's network-header offset after device header creation. pskb_expand_head() updates that offset when it relocates the head.
From the CVE record · Linux
The Linux kernel's PPPoE send path can retain a header pointer after a device callback reallocates the packet buffer. During a PPPoE send, if the first non-Ethernet port is added to an empty team device while the send is blocked in copy_from_user(), the subsequent write can target freed memory. The input does not specify authentication requirements.
Engineers running Linux kernels with PPPoE and team devices should check their kernel versions; affected versions are not specified.