CVE-2026-72454

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 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:

i3c: mipi-i3c-hci: Fix race in i3c_hci_addr_to_dev()

i3c_hci_addr_to_dev() walks bus->devs.i3c, which is protected by bus.lock (rwsem). However, it is invoked from the MIPI I3C HCI IRQ handler, which cannot take bus.lock. This allows concurrent device addition/removal in the I3C core to modify the list while it is being traversed, potentially leading to use-after-free or crashes.

Remove the dependency on the bus device list and introduce a dedicated lookup table. Add an ibi_devs[] array indexed by DAT entry, maintained under hci->lock. Update the array when IBIs are enabled or disabled, so that it always reflects the set of devices allowed to generate IBIs. Also update when IBIs are freed, to cover the corner case when an IBI is freed without first being disabled (e.g. oldedev in i3c_master_add_i3c_dev_locked()).

Move i3c_hci_addr_to_dev() into core.c, reimplement it using the new array, and add a lockdep assertion to enforce that hci->lock is held by callers.

Demote a message in PIO and DMA IBI handling, from an error to a debug message, because there is a race window when the condition can arise normally.

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

Last Modified

August 17, 2026

Advisory Details (2)

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

i3c: mipi-i3c-hci: Fix race in i3c_hci_addr_to_dev() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8f851cab401c28287d536b1347d76f6e219c0db6
generic

i3c: mipi-i3c-hci: Fix race in i3c_hci_addr_to_dev() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/650716f23eac488c6696babdc7805f6a6b7427ad

Vendor Advisories for CVE-2026-72454(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 27× in last 7d / 27× 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 08:57 UTCGHSA enrichment
  2. 2026-08-19 20:34 UTCEG score recompute
  3. 2026-08-19 20:34 UTCGHSA enrichment
  4. 2026-08-19 17:04 UTCEPSS rescore
  5. 2026-08-19 08:10 UTCGHSA enrichment
  6. 2026-08-18 19:46 UTCEG score recompute
  7. 2026-08-18 19:46 UTCGHSA enrichment
  8. 2026-08-18 13:49 UTCEPSS rescore
  9. 2026-08-18 13:49 UTCEPSS rescore
  10. 2026-08-18 07:22 UTCGHSA enrichment
  11. 2026-08-17 18:59 UTCEG score recompute
  12. 2026-08-17 18:59 UTCGHSA enrichment
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-17 06:28 UTCEG score recompute
  15. 2026-08-17 06:28 UTCGHSA enrichment
  16. 2026-08-17 05:57 UTCEG score recompute 7.80
  17. 2026-08-17 05:57 UTCGHSA enrichment
  18. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  19. 2026-08-17 05:28 UTCEG score recompute
  20. 2026-08-17 05:28 UTCGHSA enrichment
  21. 2026-08-17 05:25 UTCMITRE cvelistV5
  22. 2026-08-16 14:56 UTCEPSS rescore
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-16 02:15 UTCEPSS rescore
  25. 2026-08-15 06:23 UTCNVD update
Show 2 more
  1. 2026-08-15 06:04 UTCEG score recompute
  2. 2026-08-15 06:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-72454?
CVE-2026-72454 is a high vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: i3c: mipi-i3c-hci: Fix race in i3chciaddrtodev() i3chciaddrtodev() walks bus->devs.i3c, which is protected by bus.lock (rwsem). However, it is invoked from the MIPI I3C HCI IRQ handler, which cannot take bus.lock. This allows…
When was CVE-2026-72454 disclosed?
CVE-2026-72454 was first published in the National Vulnerability Database on August 15, 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-72454 actively exploited?
CVE-2026-72454 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-72454?
CVE-2026-72454 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-72454?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72454, 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-72454

Explore →

Is Your Infrastructure Affected by CVE-2026-72454?

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