CVE-2026-68440

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-12. 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:

net: txgbe: fix heap overflow when reading module EEPROM

txgbe_read_eeprom_hostif() always copies round_up(length, 4) bytes into the caller buffer, which ethtool allocates with exactly 'length' bytes. A non-4-aligned length therefore causes an out-of-bounds write. Copy only the remaining bytes on the final dword instead.

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
3%
KEV
Not listed

Published

August 12, 2026

Last Modified

August 17, 2026

Advisory Details (2)

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

net: txgbe: fix heap overflow when reading module EEPROM - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: txgbe: fix heap overflow when reading module EEPROM - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6a905a71fd43ce8b45f05044b11491337f232c9d

Vendor Advisories for CVE-2026-68440(1)

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 34× in last 7d / 44× 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 01:54 UTCEG score recompute
  2. 2026-08-21 01:53 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 14:40 UTCGHSA enrichment
  5. 2026-08-20 03:29 UTCEG score recompute
  6. 2026-08-20 03:29 UTCGHSA enrichment
  7. 2026-08-19 17:04 UTCEPSS rescore
  8. 2026-08-19 16:18 UTCGHSA enrichment
  9. 2026-08-19 05:06 UTCGHSA enrichment
  10. 2026-08-18 17:50 UTCEG score recompute
  11. 2026-08-18 17:50 UTCGHSA enrichment
  12. 2026-08-18 13:49 UTCEPSS rescore
  13. 2026-08-18 13:49 UTCEPSS rescore
  14. 2026-08-18 06:27 UTCGHSA enrichment
  15. 2026-08-17 19:15 UTCEG score recompute
  16. 2026-08-17 19:15 UTCGHSA enrichment
  17. 2026-08-17 13:47 UTCEPSS rescore
  18. 2026-08-17 06:31 UTCEG score recompute
  19. 2026-08-17 06:31 UTCGHSA enrichment
  20. 2026-08-17 05:35 UTCEG score recompute
  21. 2026-08-17 05:35 UTCGHSA enrichment
  22. 2026-08-16 18:49 UTCEG score recompute
  23. 2026-08-16 18:49 UTCGHSA enrichment
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 14:56 UTCEPSS rescore
Show 19 more
  1. 2026-08-16 07:38 UTCEG score recompute
  2. 2026-08-16 07:38 UTCGHSA enrichment
  3. 2026-08-15 20:28 UTCGHSA enrichment
  4. 2026-08-15 09:17 UTCEG score recompute
  5. 2026-08-15 09:17 UTCGHSA enrichment
  6. 2026-08-15 01:30 UTCEPSS rescore
  7. 2026-08-14 22:06 UTCGHSA enrichment
  8. 2026-08-14 10:56 UTCEG score recompute
  9. 2026-08-14 10:56 UTCGHSA enrichment
  10. 2026-08-13 23:45 UTCEG score recompute
  11. 2026-08-13 23:45 UTCGHSA enrichment
  12. 2026-08-13 23:03 UTCEG score recompute 7.80
  13. 2026-08-13 23:03 UTCGHSA enrichment
  14. 2026-08-13 23:03 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  15. 2026-08-13 22:00 UTCEPSS rescore
  16. 2026-08-12 13:51 UTCEPSS rescore
  17. 2026-08-12 00:19 UTCNVD update
  18. 2026-08-12 00:15 UTCEG score recompute
  19. 2026-08-12 00:15 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-68440?
CVE-2026-68440 is a high vulnerability published on August 12, 2026. In the Linux kernel, the following vulnerability has been resolved: net: txgbe: fix heap overflow when reading module EEPROM txgbereadeepromhostif() always copies roundup(length, 4) bytes into the caller buffer, which ethtool allocates with exactly 'length' bytes. A non-4-aligned length therefore…
When was CVE-2026-68440 disclosed?
CVE-2026-68440 was first published in the National Vulnerability Database on August 12, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68440 actively exploited?
CVE-2026-68440 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 97.5% of all scored CVEs.
What is the CVSS score of CVE-2026-68440?
CVE-2026-68440 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-68440?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68440, 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-68440

Explore →

Is Your Infrastructure Affected by CVE-2026-68440?

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