CVE-2026-68338

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 — 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:

net/packet: avoid fanout hook re-registration after unregister

packet_set_ring() temporarily detaches a socket from packet delivery while reconfiguring its ring. It records the previous running state, clears po->num, unregisters the protocol hook when needed, drops po->bind_lock, and later restores po->num and re-registers the hook from the saved was_running value.

That unlocked window can race with NETDEV_UNREGISTER. The notifier can observe the socket as not running, skip __unregister_prot_hook(), and invalidate the per-socket binding by setting po->ifindex to -1 and clearing po->prot_hook.dev. A one-member fanout group can still retain its shared fanout hook device pointer. When packet_set_ring() resumes, re-registering solely from the stale was_running state can re-add the fanout hook after the device has been unregistered.

Treat po->ifindex == -1 as an invalidated binding after reacquiring po->bind_lock. This is distinct from ifindex 0, the normal unbound/wildcard state: ifindex -1 marks an existing device binding that was invalidated when the device was unregistered. Restore po->num as before, but do not re-register the hook if device unregister already detached the socket.

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
7%
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

net/packet: avoid fanout hook re-registration after unregister - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/packet: avoid fanout hook re-registration after unregister - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/80ec024d53a05c60ad1d08968dcf745f10c1665c
generic

net/packet: avoid fanout hook re-registration after unregister - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/50aff80475abd3533eef4320477037e6fcc6b56e
generic

net/packet: avoid fanout hook re-registration after unregister - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1bc55c29cd85818e9052f17deb287d5a11fb817f
generic

net/packet: avoid fanout hook re-registration after unregister - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0a052e0808e015e68144a9877e6ef42b952c49fa

Vendor Advisories for CVE-2026-68338(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 36× in last 7d / 48× 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 06:00 UTCEG score recompute
  2. 2026-08-21 06:00 UTCVendor advisory
  3. 2026-08-21 06:00 UTCGHSA enrichment
  4. 2026-08-20 22:56 UTCEPSS rescore
  5. 2026-08-20 17:48 UTCGHSA enrichment
  6. 2026-08-20 05:36 UTCGHSA enrichment
  7. 2026-08-19 17:24 UTCEG score recompute
  8. 2026-08-19 17:24 UTCGHSA enrichment
  9. 2026-08-19 17:04 UTCEPSS rescore
  10. 2026-08-19 16:54 UTCEG score recompute
  11. 2026-08-19 16:54 UTCGHSA enrichment
  12. 2026-08-19 07:58 UTCGHSA enrichment
  13. 2026-08-18 19:46 UTCEG score recompute
  14. 2026-08-18 19:46 UTCGHSA enrichment
  15. 2026-08-18 13:49 UTCEPSS rescore
  16. 2026-08-18 13:49 UTCEPSS rescore
  17. 2026-08-18 07:34 UTCGHSA enrichment
  18. 2026-08-17 19:20 UTCEG score recompute
  19. 2026-08-17 19:20 UTCGHSA enrichment
  20. 2026-08-17 13:47 UTCEPSS rescore
  21. 2026-08-17 06:32 UTCEG score recompute
  22. 2026-08-17 06:32 UTCGHSA enrichment
  23. 2026-08-17 05:36 UTCEG score recompute
  24. 2026-08-17 05:36 UTCGHSA enrichment
  25. 2026-08-17 00:55 UTCEG score recompute
Show 23 more
  1. 2026-08-17 00:55 UTCGHSA enrichment
  2. 2026-08-16 14:56 UTCEPSS rescore
  3. 2026-08-16 12:43 UTCEG score recompute
  4. 2026-08-16 12:43 UTCGHSA enrichment
  5. 2026-08-16 00:32 UTCGHSA enrichment
  6. 2026-08-15 12:20 UTCEG score recompute
  7. 2026-08-15 12:20 UTCGHSA enrichment
  8. 2026-08-15 01:30 UTCEPSS rescore
  9. 2026-08-15 00:08 UTCGHSA enrichment
  10. 2026-08-14 11:56 UTCEG score recompute
  11. 2026-08-14 11:56 UTCGHSA enrichment
  12. 2026-08-13 23:45 UTCEG score recompute
  13. 2026-08-13 23:45 UTCGHSA enrichment
  14. 2026-08-13 23:04 UTCEG score recompute 7.80
  15. 2026-08-13 23:04 UTCGHSA enrichment
  16. 2026-08-13 23:03 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  17. 2026-08-13 22:00 UTCEPSS rescore
  18. 2026-08-13 09:34 UTCEG score recompute
  19. 2026-08-13 09:34 UTCGHSA enrichment
  20. 2026-08-12 13:51 UTCEPSS rescore
  21. 2026-08-10 13:24 UTCNVD update
  22. 2026-08-10 12:19 UTCEG score recompute
  23. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-68338?
CVE-2026-68338 is a high vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: net/packet: avoid fanout hook re-registration after unregister packetsetring() temporarily detaches a socket from packet delivery while reconfiguring its ring. It records the previous running state, clears po->num, unregisters the…
When was CVE-2026-68338 disclosed?
CVE-2026-68338 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-68338 actively exploited?
CVE-2026-68338 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 92.6% of all scored CVEs.
What is the CVSS score of CVE-2026-68338?
CVE-2026-68338 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-68338?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68338, 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-68338

Explore →

Is Your Infrastructure Affected by CVE-2026-68338?

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