CVE-2026-68314

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:

net: mctp i3c: clean up notifier and buses if driver register fails

mctp_i3c_mod_init() registers the I3C bus notifier and then walks the existing buses with i3c_for_each_bus_locked(mctp_i3c_bus_add_new, NULL) before registering the I3C device driver. If i3c_driver_register() fails, the function returns the error directly, leaving the notifier registered and every mctp_i3c_bus object created for the existing buses allocated. The notifier is left pointing into the module that failed to load and the bus list is leaked.

Mirror the module exit path on this failure: unregister the notifier and tear down the buses that were added before returning the error.

This issue was identified during our ongoing static-analysis research while reviewing kernel code.

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 (4)

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

net: mctp i3c: clean up notifier and buses if driver register fails - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: mctp i3c: clean up notifier and buses if driver register fails - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: mctp i3c: clean up notifier and buses if driver register fails - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/49d15cfab247c0f60ce1800bdcd66850beea7b3a
generic

net: mctp i3c: clean up notifier and buses if driver register fails - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/03d1057305ef17ac3f5936ac1580bc9a1a826e14

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

Frequently asked(5)

What is CVE-2026-68314?
CVE-2026-68314 is a high vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: net: mctp i3c: clean up notifier and buses if driver register fails mctpi3cmod_init() registers the I3C bus notifier and then walks the existing buses with i3cforeachbuslocked(mctpi3cbusaddnew, NULL) before registering the I3C…
When was CVE-2026-68314 disclosed?
CVE-2026-68314 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-68314 actively exploited?
CVE-2026-68314 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-68314?
CVE-2026-68314 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-68314?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68314, 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-68314

Explore →

Is Your Infrastructure Affected by CVE-2026-68314?

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