Answer in brief
CVE-2026-68121 records a Unknown severity vulnerability in pppoe: reload header pointer after dev_hard_header(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e6493a4d1ee17595766165fa446d45b7e0c318d0 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7e9fbd7f96bcde63a7c798fe16b38cedee7a1501 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6866abf59976d273164a6624234d96a967280223 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <bed4caecd723693f750e13adbb2c42ca1249a3fd || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e9c238f6fe42fb1b4dba3a578277de32cb487937 | e6493a4d1ee17595766165fa446d45b7e0c318d0, 7e9fbd7f96bcde63a7c798fe16b38cedee7a1501, 6866abf59976d273164a6624234d96a967280223, bed4caecd723693f750e13adbb2c42ca1249a3fd, e9c238f6fe42fb1b4dba3a578277de32cb487937 |
| Linux/Linuxgeneric | 2.6.12 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-68121 records a Unknown severity vulnerability in pppoe: reload header pointer after dev_hard_header(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e6493a4d1ee17595766165fa446d45b7e0c318d0 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7e9fbd7f96bcde63a7c798fe16b38cedee7a1501 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6866abf59976d273164a6624234d96a967280223 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <bed4caecd723693f750e13adbb2c42ca1249a3fd || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e9c238f6fe42fb1b4dba3a578277de32cb487937 | e6493a4d1ee17595766165fa446d45b7e0c318d0, 7e9fbd7f96bcde63a7c798fe16b38cedee7a1501, 6866abf59976d273164a6624234d96a967280223, bed4caecd723693f750e13adbb2c42ca1249a3fd, e9c238f6fe42fb1b4dba3a578277de32cb487937 |
| Linux/Linuxgeneric | 2.6.12 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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.
Quoted source text, attributed separately from HOL analysis.