CyberRota Analysis
AI-GeneratedA vulnerability in the Linux kernel affects the PPPoE implementation, where a stale pointer to the PPPoE header can lead to writing data into a freed memory area after device header callbacks reallocate the socket buffer (skb) head. This can result in potential memory corruption and unpredictable behavior, which may be exploited by attackers to execute arbitrary code or cause denial of service. Organizations using Linux systems with PPPoE should prioritize addressing this vulnerability to mitigate risks associated with memory management issues.
Original NVD Description
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.