CVE-2026-68397

HIGHPre-NVD 8.88.8
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.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: 8.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/iucv: take a reference on the socket found in afiucv_hs_rcv()

afiucv_hs_rcv() looks up the destination socket under iucv_sk_list.lock, drops the lock, and then passes the socket to the afiucv_hs_callback_*() handlers without holding a reference. AF_IUCV sockets are not RCU-protected and are freed synchronously by iucv_sock_kill() -> sock_put(), so a concurrent close can free the socket in the window between read_unlock() and the handler, which then dereferences freed memory (for example sk->sk_data_ready() in afiucv_hs_callback_syn()).

Take a reference with sock_hold() while the socket is still on the list and release it with sock_put() once the handler has run.

CVSS v3
8.8
EG Score
8.8(high)
EG Risk
44(Track)
EG Risk 44/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
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
19%
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/iucv: take a reference on the socket found in afiucv_hs_rcv() - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/iucv: take a reference on the socket found in afiucv_hs_rcv() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5595ea59cdf29182cf6a270cacc1426c57b603de
generic

net/iucv: take a reference on the socket found in afiucv_hs_rcv() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4fa349156043dc119721d067329714179f501749
generic

net/iucv: take a reference on the socket found in afiucv_hs_rcv() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4dc0e63abf8bc7ba8892e617c1fb8b204361e022
generic

net/iucv: take a reference on the socket found in afiucv_hs_rcv() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1801cb20a5025a787d6853e19c38db138344b4b4

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

Frequently asked(5)

What is CVE-2026-68397?
CVE-2026-68397 is a high vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: net/iucv: take a reference on the socket found in afiucvhsrcv() afiucvhsrcv() looks up the destination socket under iucvsklist.lock, drops the lock, and then passes the socket to the afiucvhscallback_*() handlers without holding a…
When was CVE-2026-68397 disclosed?
CVE-2026-68397 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-68397 actively exploited?
CVE-2026-68397 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 81.4% of all scored CVEs.
What is the CVSS score of CVE-2026-68397?
CVE-2026-68397 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-68397?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68397, 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-68397

Explore →

Is Your Infrastructure Affected by CVE-2026-68397?

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