System hang and use-after-free via IDXD cleanup
Published Aug 15, 2026 · Updated Aug 15, 2026
Use-after-free in the Linux kernel allows attackers to hang the system or access freed memory through an IDXD file-device setup failure. In idxd_cdev_open(), failed_dev_add and failed_dev_name call put_device() while wq->wq_lock is held, causing the synchronous release callback to retake that lock; cleanup then falls through and reuses and frees ctx after the callback already freed it. Reachability requires the IDXD character-device open path and a file-device setup failure; the reported consequences are a deadlock and invalid cleanup on freed memory.
Summary
What happened
Use-after-free in the Linux kernel allows attackers to hang the system or access freed memory through an IDXD file-device setup failure. In idxd_cdev_open(), failed_dev_add and failed_dev_name call put_device() while wq->wq_lock is held, causing the synchronous release callback to retake that lock; cleanup then falls through and reuses and frees ctx after the callback already freed it. Reachability requires the IDXD character-device open path and a file-device setup failure; the reported consequences are a deadlock and invalid cleanup on freed memory.
The record
- CVE
- CVE-2026-74574
- Published
- Aug 15, 2026
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416, T1499.004
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Aug 15, 2026CVE publishedPublication date reported by the CVE source.
- Aug 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.4
- Affected versionversion=e6fd6d7e5f0fe4a17a08e892afb5db800e7794ec <0679c0c189d2548f00e1bac95be28e2df5c6c7f7
- Affected versionversion=e6fd6d7e5f0fe4a17a08e892afb5db800e7794ec <6e26a41c4c1a706edaaa7c7dffc6b3b945707a55
- Affected versionversion=e6fd6d7e5f0fe4a17a08e892afb5db800e7794ec <778ccbded2c8749c5be7f0dfa04fc9977a36fb7e
- Affected versionversion=e6fd6d7e5f0fe4a17a08e892afb5db800e7794ec <8d5d28285728be47c82fdf1c48be4268293c90e7
- Affected versionversion=e6fd6d7e5f0fe4a17a08e892afb5db800e7794ec <ee1d7274102285d78a53161fc705a8d8cd40b066
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo