CVE-2026-74574

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

HIGH
7.8
CVSS Score
Published: August 15, 2026 at 12:28 PM UTC
Updated: October 16, 2026 at 08:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.4e6fd6d7e5f0fe4a17a08e892afb5db800e7794ec
Vendor states this is fixed in 0679c0c189d2548f00e1bac95be28e2df5c6c7f7 (fixed)
Vendor states this is fixed in 6e26a41c4c1a706edaaa7c7dffc6b3b945707a55 (fixed)
Vendor states this is fixed in 778ccbded2c8749c5be7f0dfa04fc9977a36fb7e (fixed)
Vendor states this is fixed in 8d5d28285728be47c82fdf1c48be4268293c90e7 (fixed)
Vendor states this is fixed in ee1d7274102285d78a53161fc705a8d8cd40b066 (fixed)
Vendor states this is fixed in 6.12.103 (unaffected)
Vendor states this is fixed in 6.18.44 (unaffected)
Vendor states this is fixed in 6.4 (unaffected)
Vendor states this is fixed in 6.6.151 (unaffected)
Vendor states this is fixed in 7.1.8 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card