CVE-2026-74668

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 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:

packet: use consistent hard_header_len in TX_RING send path

tpacket_snd() reads dev->hard_header_len independently for skb allocation and header construction in tpacket_fill_skb(). Concurrent netdevice reconfiguration can therefore make the reserved headroom smaller than the amount later pushed, or make copylen - hard_header_len negative.

Snapshot hard_header_len once before processing ring frames and use it for the frame limit, headroom allocation, copy length, and skb construction. Pass the snapshot to tpacket_fill_skb().

The separate SOCK_DGRAM consistency problem between hard_header_len and header_ops->create is not addressed here.

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 22, 2026

Last Modified

August 27, 2026

Advisory Details (5)

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

packet: use consistent hard_header_len in TX_RING send path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/21b5953e7494c16a42e6cd8cf110e18d13ae4a6b
generic

packet: use consistent hard_header_len in TX_RING send path - kernel/git/stable/linux.git - Linux kernel stable tree

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

packet: use consistent hard_header_len in TX_RING send path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/27e068d1b35dbec10a3cf268887c94407be4badc
generic

packet: use consistent hard_header_len in TX_RING send path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/016763e829cac37b3234eace86fd0a4c560de4a7
generic

packet: use consistent hard_header_len in TX_RING send path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d85d2fd54e901637c81d847811e03c662aee13cd

Vendor Advisories for CVE-2026-74668(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 28× in last 7d / 31× 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-30 01:22 UTCEPSS rescore
  2. 2026-08-29 23:28 UTCGHSA enrichment
  3. 2026-08-29 12:13 UTCGHSA enrichment
  4. 2026-08-29 00:49 UTCEG score recompute
  5. 2026-08-29 00:49 UTCGHSA enrichment
  6. 2026-08-28 21:42 UTCEPSS rescore
  7. 2026-08-28 12:01 UTCGHSA enrichment
  8. 2026-08-28 00:47 UTCEG score recompute
  9. 2026-08-28 00:47 UTCGHSA enrichment
  10. 2026-08-27 14:25 UTCEPSS rescore
  11. 2026-08-27 13:33 UTCEG score recompute
  12. 2026-08-27 13:33 UTCGHSA enrichment
  13. 2026-08-27 13:00 UTCEG score recompute
  14. 2026-08-27 13:00 UTCGHSA enrichment
  15. 2026-08-27 03:27 UTCGHSA enrichment
  16. 2026-08-26 16:13 UTCEG score recompute
  17. 2026-08-26 16:13 UTCGHSA enrichment
  18. 2026-08-26 14:47 UTCEPSS rescore
  19. 2026-08-26 04:57 UTCGHSA enrichment
  20. 2026-08-25 17:44 UTCEG score recompute
  21. 2026-08-25 17:44 UTCGHSA enrichment
  22. 2026-08-25 13:49 UTCEPSS rescore
  23. 2026-08-25 06:29 UTCEG score recompute
  24. 2026-08-25 06:29 UTCGHSA enrichment
  25. 2026-08-25 05:56 UTCEG score recompute▲ 7.80
Show 6 more
  1. 2026-08-25 05:56 UTCGHSA enrichment
  2. 2026-08-25 05:55 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  3. 2026-08-24 14:18 UTCEPSS rescore
  4. 2026-08-22 16:24 UTCNVD update
  5. 2026-08-22 15:41 UTCEG score recompute
  6. 2026-08-22 15:35 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74668?
CVE-2026-74668 is a high vulnerability published on August 22, 2026. In the Linux kernel, the following vulnerability has been resolved: packet: use consistent hardheaderlen in TX_RING send path tpacketsnd() reads dev->hardheader_len independently for skb allocation and header construction in tpacketfillskb(). Concurrent netdevice reconfiguration can therefore make…
When was CVE-2026-74668 disclosed?
CVE-2026-74668 was first published in the National Vulnerability Database on August 22, 2026, with the most recent update on August 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74668 actively exploited?
CVE-2026-74668 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.1% of all scored CVEs.
What is the CVSS score of CVE-2026-74668?
CVE-2026-74668 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-74668?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74668, 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-74668

Explore →

Is Your Infrastructure Affected by CVE-2026-74668?

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

Start Free Scan →Browse All CVEs