CVE-2026-68140

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: fix use-after-free of a severed iucv_path

af_iucv queues not-yet-received message notifications on iucv->message_q, each holding a raw pointer to the connection's iucv_path. When the peer severs the connection, iucv_sever_path() frees that path with iucv_path_free() but leaves the notifications queued. A later recvmsg() drains message_q via iucv_process_message_q() and hands the stale path to message_receive() -- a use-after-free of the freed iucv_path.

Drop the queued notifications when the path is severed; once the path is gone they can no longer be received. This also frees the notifications leaked when a socket is closed with messages still queued.

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
20%
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: fix use-after-free of a severed iucv_path - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/iucv: fix use-after-free of a severed iucv_path - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/iucv: fix use-after-free of a severed iucv_path - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/iucv: fix use-after-free of a severed iucv_path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/900cd6d8119b7f3ae5c4bf82f922ff5957df43db
generic

net/iucv: fix use-after-free of a severed iucv_path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/23658b350b4107e8292045c2044983fd426fa15d

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

Frequently asked(5)

What is CVE-2026-68140?
CVE-2026-68140 is a high vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: net/iucv: fix use-after-free of a severed iucv_path afiucv queues not-yet-received message notifications on iucv->messageq, each holding a raw pointer to the connection's iucv_path. When the peer severs the connection,…
When was CVE-2026-68140 disclosed?
CVE-2026-68140 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-68140 actively exploited?
CVE-2026-68140 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 79.8% of all scored CVEs.
What is the CVSS score of CVE-2026-68140?
CVE-2026-68140 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-68140?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68140, 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-68140

Explore →

Is Your Infrastructure Affected by CVE-2026-68140?

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