CVE-2026-68121

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM 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 — Patch released 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.3%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100CISA SSVC

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%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
20th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 10, 2026

Last Modified

August 19, 2026

Advisory Details (5)

Auto-updated Aug 14, 2026
Patch available.
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

Patch Availability(16)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:6.12.0-259.27.el10nv2026-09-30redhat
redhatkernel-0:5.14.0-687.52.1.el9_82026-09-25redhat
redhatkernel-0:4.18.0-305.209.1.el8_42026-09-24redhat
redhatkernel-0:5.14.0-570.144.1.el9_62026-09-24redhat
redhatkernel-0:2.6.32-754.63.1.el62026-09-24redhat
redhatkernel-0:3.10.0-1160.164.1.el72026-09-24redhat
redhatkernel-rt-0:5.14.0-284.194.1.rt14.479.el9_22026-09-24redhat
redhatkernel-0:4.18.0-372.218.1.el8_62026-09-24redhat
redhatkernel-0:4.18.0-477.170.1.el8_82026-09-24redhat
redhatkernel-0:5.14.0-427.152.1.el9_42026-09-24redhat
redhatkernel-0:6.12.0-211.60.1.el10_22026-09-24redhat
redhatkernel-0:6.12.0-55.107.1.el10_02026-09-24redhat
redhatkernel-rt-0:3.10.0-1160.164.1.rt56.1316.el72026-09-24redhat
redhatkernel-rt-0:4.18.0-553.168.1.rt7.509.el8_102026-09-24redhat
redhatkernel-0:5.14.0-284.194.1.el9_22026-09-24redhat
redhatkernel-0:4.18.0-553.168.1.el8_102026-09-24redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (56 versions)
  • every version up to 6.1.187-1: fixed in 6.1.187-1
—
linux-6.126.12.100-1~deb12u1
  • every version up to 6.12.101-1~deb12u1: fixed in 6.12.101-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (32 versions)
  • every version up to 6.12.101-1: fixed in 6.12.101-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (161 versions)
  • every version up to 7.1.6-1: fixed in 7.1.6-1
—

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 28× in last 7d / 136× 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.

Showing the most recent 100 of 259 total refreshes for this CVE.

  1. 2026-10-05 07:53 UTCEG score recompute
  2. 2026-10-05 07:53 UTCVendor advisory
  3. 2026-10-05 07:53 UTCGHSA enrichment
  4. 2026-10-04 23:22 UTCEPSS rescore
  5. 2026-10-04 16:44 UTCVendor advisory
  6. 2026-10-04 16:44 UTCGHSA enrichment
  7. 2026-10-04 05:27 UTCEG score recompute
  8. 2026-10-04 05:27 UTCVendor advisory
  9. 2026-10-04 05:27 UTCGHSA enrichment
  10. 2026-10-03 14:26 UTCEPSS rescore
  11. 2026-10-03 00:56 UTCEG score recompute
  12. 2026-10-03 00:56 UTCVendor advisory
  13. 2026-10-03 00:56 UTCGHSA enrichment
  14. 2026-10-02 17:56 UTCEPSS rescore
  15. 2026-10-02 09:24 UTCEG score recompute
  16. 2026-10-02 09:24 UTCVendor advisory
  17. 2026-10-02 09:24 UTCGHSA enrichment
  18. 2026-10-01 19:50 UTCEPSS rescore
  19. 2026-10-01 10:08 UTCVendor advisory
  20. 2026-10-01 10:08 UTCGHSA enrichment
  21. 2026-09-30 22:43 UTCEG score recompute
  22. 2026-09-30 22:43 UTCVendor advisory
  23. 2026-09-30 22:43 UTCGHSA enrichment
  24. 2026-09-30 15:03 UTCEPSS rescore
  25. 2026-09-29 05:26 UTCEG score recompute
Show 75 more
  1. 2026-09-29 05:26 UTCVendor advisory
  2. 2026-09-29 05:26 UTCGHSA enrichment
  3. 2026-09-28 13:52 UTCEPSS rescore
  4. 2026-09-28 04:03 UTCVendor advisory
  5. 2026-09-28 04:03 UTCGHSA enrichment
  6. 2026-09-27 16:58 UTCEG score recompute
  7. 2026-09-27 16:58 UTCVendor advisory
  8. 2026-09-27 16:58 UTCGHSA enrichment
  9. 2026-09-27 13:48 UTCEPSS rescore
  10. 2026-09-26 15:59 UTCEPSS rescore
  11. 2026-09-25 04:06 UTCEG score recompute
  12. 2026-09-25 04:06 UTCVendor advisory
  13. 2026-09-25 04:06 UTCGHSA enrichment
  14. 2026-09-24 08:17 UTCVendor advisory
  15. 2026-09-24 08:17 UTCGHSA enrichment
  16. 2026-09-23 21:13 UTCEG score recompute
  17. 2026-09-23 21:13 UTCVendor advisory
  18. 2026-09-23 21:13 UTCGHSA enrichment
  19. 2026-09-23 17:54 UTCEPSS rescore
  20. 2026-09-23 08:34 UTCVendor advisory
  21. 2026-09-23 08:34 UTCGHSA enrichment
  22. 2026-09-22 21:29 UTCEG score recompute
  23. 2026-09-22 21:29 UTCVendor advisory
  24. 2026-09-22 21:29 UTCGHSA enrichment
  25. 2026-09-22 10:25 UTCVendor advisory
  26. 2026-09-22 10:25 UTCGHSA enrichment
  27. 2026-09-21 23:16 UTCEG score recompute
  28. 2026-09-21 23:16 UTCVendor advisory
  29. 2026-09-21 23:16 UTCGHSA enrichment
  30. 2026-09-21 11:17 UTCVendor advisory
  31. 2026-09-21 11:17 UTCGHSA enrichment
  32. 2026-09-20 22:45 UTCEG score recompute
  33. 2026-09-20 22:45 UTCVendor advisory
  34. 2026-09-20 22:45 UTCGHSA enrichment
  35. 2026-09-20 20:16 UTCEPSS rescore
  36. 2026-09-20 10:53 UTCVendor advisory
  37. 2026-09-20 10:53 UTCGHSA enrichment
  38. 2026-09-19 23:48 UTCEG score recompute
  39. 2026-09-19 23:48 UTCVendor advisory
  40. 2026-09-19 23:48 UTCGHSA enrichment
  41. 2026-09-19 12:44 UTCVendor advisory
  42. 2026-09-19 12:44 UTCGHSA enrichment
  43. 2026-09-19 00:16 UTCEG score recompute
  44. 2026-09-19 00:16 UTCVendor advisory
  45. 2026-09-19 00:16 UTCGHSA enrichment
  46. 2026-09-18 19:28 UTCEPSS rescore
  47. 2026-09-18 13:12 UTCVendor advisory
  48. 2026-09-18 13:12 UTCGHSA enrichment
  49. 2026-09-18 02:08 UTCEG score recompute
  50. 2026-09-18 02:08 UTCVendor advisory
  51. 2026-09-18 02:08 UTCGHSA enrichment
  52. 2026-09-17 15:03 UTCVendor advisory
  53. 2026-09-17 15:03 UTCGHSA enrichment
  54. 2026-09-17 00:49 UTCEG score recompute
  55. 2026-09-17 00:49 UTCVendor advisory
  56. 2026-09-17 00:49 UTCGHSA enrichment
  57. 2026-09-16 14:08 UTCEPSS rescore
  58. 2026-09-16 05:15 UTCEPSS rescore
  59. 2026-09-16 02:39 UTCVendor advisory
  60. 2026-09-16 02:39 UTCGHSA enrichment
  61. 2026-09-15 14:05 UTCEG score recompute
  62. 2026-09-15 14:05 UTCVendor advisory
  63. 2026-09-15 14:05 UTCGHSA enrichment
  64. 2026-09-15 00:44 UTCVendor advisory
  65. 2026-09-15 00:44 UTCGHSA enrichment
  66. 2026-09-14 10:11 UTCVendor advisory
  67. 2026-09-14 10:11 UTCGHSA enrichment
  68. 2026-09-13 23:00 UTCEG score recompute
  69. 2026-09-13 23:00 UTCVendor advisory
  70. 2026-09-13 23:00 UTCGHSA enrichment
  71. 2026-09-13 11:56 UTCVendor advisory
  72. 2026-09-13 11:56 UTCGHSA enrichment
  73. 2026-09-13 00:52 UTCEG score recompute
  74. 2026-09-13 00:52 UTCVendor advisory
  75. 2026-09-13 00:52 UTCGHSA enrichment

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 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.3% probability of exploitation in the next 30 days (20th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-68121?
CVE-2026-68121 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-68121?
A fix for CVE-2026-68121 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-68121 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.