0.0
NA
CVE-2026-74574
dmaengine: idxd: fix fdev setup failure cleanup in idxd_cdev_open()
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.

INFO

Published Date :

Aug. 15, 2026, 1:18 p.m.

Last Modified :

Aug. 15, 2026, 1:18 p.m.

Remotely Exploit :

No

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products

The following products are affected by CVE-2026-74574 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

No affected product recoded yet

Solution
Fix deadlock and use-after-free by adjusting device reference counting and cleanup paths.
  • Ensure wq->wq_lock is unlocked before put_device(fdev).
  • Return directly from file-device setup failure paths.
  • Let release callback handle context cleanup.
  • Move idxd_wq_get() before file-device setup.
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-74574 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-74574 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-74574 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-74574 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Aug. 15, 2026

    Action Type Old Value New Value
    Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': 'e6fd6d7e5f0fe4a17a08e892afb5db800e7794ec', 'lessThan': '778ccbded2c8749c5be7f0dfa04fc9977a36fb7e', 'versionType': 'git'}, {'status': 'affected', 'version': 'e6fd6d7e5f0fe4a17a08e892afb5db800e7794ec', 'lessThan': '8d5d28285728be47c82fdf1c48be4268293c90e7', 'versionType': 'git'}, {'status': 'affected', 'version': 'e6fd6d7e5f0fe4a17a08e892afb5db800e7794ec', 'lessThan': '0679c0c189d2548f00e1bac95be28e2df5c6c7f7', 'versionType': 'git'}, {'status': 'affected', 'version': 'e6fd6d7e5f0fe4a17a08e892afb5db800e7794ec', 'lessThan': '6e26a41c4c1a706edaaa7c7dffc6b3b945707a55', 'versionType': 'git'}, {'status': 'affected', 'version': 'e6fd6d7e5f0fe4a17a08e892afb5db800e7794ec', 'lessThan': 'ee1d7274102285d78a53161fc705a8d8cd40b066', 'versionType': 'git'}], 'programFiles': ['drivers/dma/idxd/cdev.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '6.4'}, {'status': 'unaffected', 'version': '0', 'lessThan': '6.4', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '6.6.151', 'versionType': 'semver', 'lessThanOrEqual': '6.6.*'}, {'status': 'unaffected', 'version': '6.12.103', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.44', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.1.8', 'versionType': 'semver', 'lessThanOrEqual': '7.1.*'}, {'status': 'unaffected', 'version': '7.2-rc6', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['drivers/dma/idxd/cdev.c'], 'defaultStatus': 'affected'}]
    Added 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.
    Added Reference https://git.kernel.org/stable/c/0679c0c189d2548f00e1bac95be28e2df5c6c7f7
    Added Reference https://git.kernel.org/stable/c/6e26a41c4c1a706edaaa7c7dffc6b3b945707a55
    Added Reference https://git.kernel.org/stable/c/778ccbded2c8749c5be7f0dfa04fc9977a36fb7e
    Added Reference https://git.kernel.org/stable/c/8d5d28285728be47c82fdf1c48be4268293c90e7
    Added Reference https://git.kernel.org/stable/c/ee1d7274102285d78a53161fc705a8d8cd40b066
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.