CVE-2026-68399

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:

bpf: Fix UAF in sock clone early bailouts

Similar to recent commit 9b51a6155d14 ("bpf,fork: wipe ->bpf_storage before bailouts that access it"), sk_clone() performs an initial shallow copy of the socket field ->sk_bpf_storage via sock_copy() for the cloned socket newsk.

If sk_clone() bails out early (e.g. if sk_filter_charge() fails) prior to calling bpf_sk_storage_clone(), newsk->sk_bpf_storage still points to the parent socket's BPF local storage. When newsk is subsequently freed via sk_free(), the deallocation path (__sk_destruct() -> bpf_sk_storage_free()) destroys the parent socket's BPF local storage, leading to a use-after-free (UAF) on the parent socket.

Fix this by resetting newsk->sk_bpf_storage to NULL immediately after sock_copy() in sk_clone(), and remove the now redundant initialization from bpf_sk_storage_clone().

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

Last Modified

August 17, 2026

Advisory Details (2)

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

bpf: Fix UAF in sock clone early bailouts - kernel/git/stable/linux.git - Linux kernel stable tree

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

bpf: Fix UAF in sock clone early bailouts - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/14b49b5ab29979552c219a09e569b424fbbf4a6e

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

Frequently asked(5)

What is CVE-2026-68399?
CVE-2026-68399 is a high vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: bpf: Fix UAF in sock clone early bailouts Similar to recent commit 9b51a6155d14 ("bpf,fork: wipe ->bpf_storage before bailouts that access it"), sk_clone() performs an initial shallow copy of the socket field ->skbpfstorage via…
When was CVE-2026-68399 disclosed?
CVE-2026-68399 was first published in the National Vulnerability Database on August 10, 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-68399 actively exploited?
CVE-2026-68399 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.0% of all scored CVEs.
What is the CVSS score of CVE-2026-68399?
CVE-2026-68399 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-68399?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68399, 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-68399

Explore →

Is Your Infrastructure Affected by CVE-2026-68399?

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