Vulnerability · CVE-2026-68121
pppoe: reload header pointer after dev_hard_header()
Published Aug 10, 2026 · catalog updated Oct 17, 2026 · pppoe: reload header pointer
Check if you run it
No confirmed exploitation is on record for CVE-2026-68121. EPSS is 0.30%. Act only if a listed version of pppoe: reload header pointer is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (pppoe: reload header pointer).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- High7.8
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.30%
- Remediation
- Not established
- Affected products
- Linux Kernel
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.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- Linux Kernel2.6.12 → 5.10.265
- Linux Kernel2.6.12 → 5.10.265; 5.11.0 → 5.15.216; 5.16.0 → 6.1.183
How to fix CVE-2026-68121
Recommended remediation
No required-action text, fix commit, or clear fixed-version range is stored yet.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-68121. EPSS is 0.30%. Act only if a listed version of pppoe: reload header pointer is installed.
Which versions are affected?
Compare what you have installed with Kernel 2.6.12 → 5.10.265; Kernel 2.6.12 → 5.10.265; 5.11.0 → 5.15.216; 5.16.0 → 6.1.183. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 0.30%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Aug 10, 2026 · OpenSSF OSV / OSV Scanner
Detected
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 ad
Oct 16, 2026 · OpenSSF OSV / OSV Scanner
Fix available
Kernel fixed in 5.10.265
Oct 16, 2026 · OpenSSF OSV / OSV Scanner
Fix available
Kernel fixed in 5.10.265
Oct 16, 2026 · OpenSSF OSV / OSV Scanner
Updated
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 ad
Oct 17, 2026 · OpenSSF OSV / OSV Scanner
Fix available
Kernel fixed in 5.10.265; Kernel fixed in 5.15.216; Kernel fixed in 6.1.183; Kernel fixed in 6.6.148
Oct 17, 2026 · OpenSSF OSV / OSV Scanner
Fix available
Kernel fixed in 5.10.265; 5.11.0
Oct 17, 2026 · OpenSSF OSV / OSV Scanner
Updated
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 ad
Sources
- CVE.orgVulnerability recordCVE-2026-68121
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2026-68121
30-day exploitation probability 0.3%
first.org - OpenSSF OSV / OSV ScannerPackage advisoryCVE-2026-68121
pppoe: reload header pointer after dev_hard_header()
osv.dev
References
Freshness
Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.