CVE-2026-74617

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
9.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: 9.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:

dibs: initialise dibs->lock in dibs_dev_alloc()

dibs->lock is initialised by dibs_dev_add(), but a dibs device can already take interrupts before that call: ism_probe() runs ism_dev_init(), and hence request_irq(), before it calls dibs_dev_add(). No client can have registered a dmb at that point, so no dmb interrupt can occur, but a GID event interrupt can, and ism_handle_irq() takes dibs->lock unconditionally on entry, before it inspects anything else.

Initialise the lock in dibs_dev_alloc() instead, so that it is valid as soon as a driver can publish the device to its interrupt handler.

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
49(Track)
EG Risk 49/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
Severity98% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
37%
KEV
Not listed

Published

August 22, 2026

Last Modified

August 25, 2026

Advisory Details (3)

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

dibs: initialise dibs->lock in dibs_dev_alloc() - kernel/git/stable/linux.git - Linux kernel stable tree

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

dibs: initialise dibs->lock in dibs_dev_alloc() - kernel/git/stable/linux.git - Linux kernel stable tree

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

dibs: initialise dibs->lock in dibs_dev_alloc() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2926031acba100d0c18fcfaa7a2ed29609318848

Vendor Advisories for CVE-2026-74617(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 45× in last 7d / 48× 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-30 05:50 UTCGHSA enrichment
  2. 2026-08-30 01:45 UTCEG score recompute
  3. 2026-08-30 01:45 UTCGHSA enrichment
  4. 2026-08-30 01:22 UTCEPSS rescore
  5. 2026-08-29 21:40 UTCGHSA enrichment
  6. 2026-08-29 17:36 UTCGHSA enrichment
  7. 2026-08-29 13:12 UTCGHSA enrichment
  8. 2026-08-29 09:06 UTCGHSA enrichment
  9. 2026-08-29 05:02 UTCGHSA enrichment
  10. 2026-08-29 00:53 UTCEG score recompute
  11. 2026-08-29 00:53 UTCGHSA enrichment
  12. 2026-08-28 21:42 UTCEPSS rescore
  13. 2026-08-28 16:30 UTCGHSA enrichment
  14. 2026-08-28 12:07 UTCGHSA enrichment
  15. 2026-08-28 08:04 UTCGHSA enrichment
  16. 2026-08-28 03:55 UTCGHSA enrichment
  17. 2026-08-27 23:48 UTCGHSA enrichment
  18. 2026-08-27 19:44 UTCGHSA enrichment
  19. 2026-08-27 15:40 UTCEG score recompute
  20. 2026-08-27 15:40 UTCGHSA enrichment
  21. 2026-08-27 14:25 UTCEPSS rescore
  22. 2026-08-27 11:31 UTCGHSA enrichment
  23. 2026-08-27 07:27 UTCGHSA enrichment
  24. 2026-08-27 03:22 UTCGHSA enrichment
  25. 2026-08-26 23:15 UTCGHSA enrichment
Show 23 more
  1. 2026-08-26 19:10 UTCGHSA enrichment
  2. 2026-08-26 15:07 UTCEG score recompute
  3. 2026-08-26 15:07 UTCGHSA enrichment
  4. 2026-08-26 14:47 UTCEPSS rescore
  5. 2026-08-26 10:59 UTCGHSA enrichment
  6. 2026-08-26 06:56 UTCGHSA enrichment
  7. 2026-08-26 02:52 UTCGHSA enrichment
  8. 2026-08-25 22:47 UTCGHSA enrichment
  9. 2026-08-25 18:43 UTCGHSA enrichment
  10. 2026-08-25 14:39 UTCEG score recompute
  11. 2026-08-25 14:39 UTCGHSA enrichment
  12. 2026-08-25 13:49 UTCEPSS rescore
  13. 2026-08-25 10:35 UTCEG score recompute
  14. 2026-08-25 10:35 UTCGHSA enrichment
  15. 2026-08-25 06:30 UTCEG score recompute
  16. 2026-08-25 06:30 UTCGHSA enrichment
  17. 2026-08-25 05:45 UTCEG score recompute▲ 9.80
  18. 2026-08-25 05:45 UTCGHSA enrichment
  19. 2026-08-25 05:45 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  20. 2026-08-24 14:18 UTCEPSS rescore
  21. 2026-08-22 16:24 UTCNVD update
  22. 2026-08-22 15:42 UTCEG score recompute
  23. 2026-08-22 15:35 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74617?
CVE-2026-74617 is a critical vulnerability published on August 22, 2026. In the Linux kernel, the following vulnerability has been resolved: dibs: initialise dibs->lock in dibsdevalloc() dibs->lock is initialised by dibsdevadd(), but a dibs device can already take interrupts before that call: ism_probe() runs ismdevinit(), and hence request_irq(), before it calls…
When was CVE-2026-74617 disclosed?
CVE-2026-74617 was first published in the National Vulnerability Database on August 22, 2026, with the most recent update on August 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74617 actively exploited?
CVE-2026-74617 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 63.2% of all scored CVEs.
What is the CVSS score of CVE-2026-74617?
CVE-2026-74617 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-74617?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74617, 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-74617

Explore →

Is Your Infrastructure Affected by CVE-2026-74617?

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

Start Free Scan →Browse All CVEs