CVE-2026-74574

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:

dmaengine: idxd: fix fdev setup failure cleanup in idxd_cdev_open()

The failed_dev_add and failed_dev_name paths drop the file-device reference while wq->wq_lock is still held. If put_device(fdev) drops the last reference, idxd_file_dev_release() runs synchronously and tries to take wq->wq_lock again, deadlocking.

Those paths also fall through into the later ctx cleanup labels even though idxd_file_dev_release() owns that cleanup and frees ctx. This can make idxd_xa_pasid_remove(ctx) and kfree(ctx) operate on a freed context.

Move idxd_wq_get() before file-device setup can fail, since the release callback always calls idxd_wq_put(). Then unlock wq->wq_lock before put_device(fdev) and return directly from the file-device setup failure path, leaving ctx cleanup to the release callback.

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
2%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (5)

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

dmaengine: idxd: fix fdev setup failure cleanup in idxd_cdev_open() - kernel/git/stable/linux.git - Linux kernel stable tree

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

dmaengine: idxd: fix fdev setup failure cleanup in idxd_cdev_open() - kernel/git/stable/linux.git - Linux kernel stable tree

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

dmaengine: idxd: fix fdev setup failure cleanup in idxd_cdev_open() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/778ccbded2c8749c5be7f0dfa04fc9977a36fb7e
generic

dmaengine: idxd: fix fdev setup failure cleanup in idxd_cdev_open() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6e26a41c4c1a706edaaa7c7dffc6b3b945707a55
generic

dmaengine: idxd: fix fdev setup failure cleanup in idxd_cdev_open() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0679c0c189d2548f00e1bac95be28e2df5c6c7f7

Vendor Advisories for CVE-2026-74574(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-21 05:13 UTCEG score recompute
  2. 2026-08-21 05:13 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 17:36 UTCGHSA enrichment
  5. 2026-08-20 05:58 UTCGHSA enrichment
  6. 2026-08-19 18:21 UTCEG score recompute
  7. 2026-08-19 18:21 UTCGHSA enrichment
  8. 2026-08-19 17:04 UTCEPSS rescore
  9. 2026-08-19 05:46 UTCGHSA enrichment
  10. 2026-08-18 18:09 UTCGHSA enrichment
  11. 2026-08-18 06:30 UTCGHSA enrichment
  12. 2026-08-17 18:53 UTCEG score recompute
  13. 2026-08-17 18:53 UTCGHSA enrichment
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-17 06:23 UTCEG score recompute
  16. 2026-08-17 06:23 UTCGHSA enrichment
  17. 2026-08-17 05:54 UTCEG score recompute 7.80
  18. 2026-08-17 05:54 UTCGHSA enrichment
  19. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  20. 2026-08-17 05:39 UTCEG score recompute
  21. 2026-08-17 05:39 UTCGHSA enrichment
  22. 2026-08-17 05:39 UTCMITRE cvelistV5
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-15 13:27 UTCNVD update
Show 2 more
  1. 2026-08-15 12:38 UTCEG score recompute
  2. 2026-08-15 12:37 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74574?
CVE-2026-74574 is a high vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: fix fdev setup failure cleanup in idxdcdevopen() The faileddevadd and faileddevname paths drop the file-device reference while wq->wqlock is still held. If putdevice(fdev) drops the last reference,…
When was CVE-2026-74574 disclosed?
CVE-2026-74574 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-74574 actively exploited?
CVE-2026-74574 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.6% of all scored CVEs.
What is the CVSS score of CVE-2026-74574?
CVE-2026-74574 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-74574?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74574, 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-74574

Explore →

Is Your Infrastructure Affected by CVE-2026-74574?

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