CVE-2026-68121

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-10. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.8
EG Score
7.8(high)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 19, 2026

Advisory Details (5)

Auto-updated Aug 14, 2026
No patch confirmed yet.
generic

pppoe: reload header pointer after dev_hard_header() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e9c238f6fe42fb1b4dba3a578277de32cb487937
generic

pppoe: reload header pointer after dev_hard_header() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e6493a4d1ee17595766165fa446d45b7e0c318d0
generic

pppoe: reload header pointer after dev_hard_header() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bed4caecd723693f750e13adbb2c42ca1249a3fd
generic

pppoe: reload header pointer after dev_hard_header() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7e9fbd7f96bcde63a7c798fe16b38cedee7a1501
generic

pppoe: reload header pointer after dev_hard_header() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6866abf59976d273164a6624234d96a967280223

Vendor Advisories for CVE-2026-68121(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 33× in last 7d / 45× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-21 02:41 UTCEG score recompute
  2. 2026-08-21 02:41 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 15:36 UTCGHSA enrichment
  5. 2026-08-20 04:30 UTCGHSA enrichment
  6. 2026-08-19 17:26 UTCEG score recompute
  7. 2026-08-19 17:26 UTCGHSA enrichment
  8. 2026-08-19 17:04 UTCEPSS rescore
  9. 2026-08-19 16:55 UTCEG score recompute
  10. 2026-08-19 16:55 UTCGHSA enrichment
  11. 2026-08-19 13:30 UTCGHSA enrichment
  12. 2026-08-19 02:25 UTCGHSA enrichment
  13. 2026-08-18 15:18 UTCEG score recompute
  14. 2026-08-18 15:18 UTCGHSA enrichment
  15. 2026-08-18 13:48 UTCEPSS rescore
  16. 2026-08-18 03:49 UTCGHSA enrichment
  17. 2026-08-17 16:45 UTCEG score recompute
  18. 2026-08-17 16:45 UTCGHSA enrichment
  19. 2026-08-17 13:47 UTCEPSS rescore
  20. 2026-08-17 05:41 UTCGHSA enrichment
  21. 2026-08-17 05:00 UTCGHSA enrichment
  22. 2026-08-16 17:56 UTCEG score recompute
  23. 2026-08-16 17:56 UTCGHSA enrichment
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 06:51 UTCEG score recompute
Show 20 more
  1. 2026-08-16 06:51 UTCGHSA enrichment
  2. 2026-08-15 19:48 UTCGHSA enrichment
  3. 2026-08-15 08:44 UTCEG score recompute
  4. 2026-08-15 08:44 UTCGHSA enrichment
  5. 2026-08-15 01:30 UTCEPSS rescore
  6. 2026-08-14 21:39 UTCGHSA enrichment
  7. 2026-08-14 10:35 UTCEG score recompute
  8. 2026-08-14 10:35 UTCGHSA enrichment
  9. 2026-08-13 23:31 UTCEG score recompute
  10. 2026-08-13 23:31 UTCGHSA enrichment
  11. 2026-08-13 22:46 UTCEG score recompute▲ 7.80
  12. 2026-08-13 22:46 UTCGHSA enrichment
  13. 2026-08-13 22:44 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  14. 2026-08-13 22:00 UTCEPSS rescore
  15. 2026-08-13 08:25 UTCEG score recompute
  16. 2026-08-13 08:25 UTCGHSA enrichment
  17. 2026-08-12 13:51 UTCEPSS rescore
  18. 2026-08-10 13:24 UTCNVD update
  19. 2026-08-10 12:21 UTCEG score recompute
  20. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-68121?
CVE-2026-68121 is a high vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: pppoe: reload header pointer after devhardheader() pppoe_sendmsg() saves a pointer to the PPPoE header before calling devhardheader(). Device header callbacks are allowed to reallocate the skb head, invalidating pointers into it.…
When was CVE-2026-68121 disclosed?
CVE-2026-68121 was first published in the National Vulnerability Database on August 10, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68121 actively exploited?
CVE-2026-68121 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 96.3% of all scored CVEs.
What is the CVSS score of CVE-2026-68121?
CVE-2026-68121 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-68121?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68121, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-68121

Explore →

Is Your Infrastructure Affected by CVE-2026-68121?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs