CVE-2026-74574

Received Received - Intake

Race Condition in Linux Kernel DMA Engine idxd Driver

Publication date: 2026-08-15

Last updated on: 2026-08-17

Assigner: kernel.org

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-08-15

Last Modified

2026-08-17

Generated

2026-09-04

AI Q&A

2026-08-15

EPSS Evaluated

2026-09-03

NVD

CVE-2026-74574

EUVD

EUVD-2026-59639

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	*

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-UNKNOWN

Attack-Flow Graph

Executive Summary

This is a Linux kernel vulnerability in the idxd (Intel Data Streaming Accelerator) subsystem. It involves a deadlock and use-after-free issue during file-device setup failure cleanup. The problem occurs when cleanup paths drop references while holding a lock, causing a deadlock if the last reference is released. It also incorrectly proceeds with context cleanup, leading to operations on freed memory.

Detection Guidance

This vulnerability is specific to the Linux kernel's dmaengine subsystem, particularly the idxd driver. Detection requires checking kernel logs for deadlock or crash events related to idxd operations. Commands like dmesg | grep idxd or journalctl -k | grep idxd may reveal errors. Ensure your kernel version is updated to a patched release.

Impact Analysis

This vulnerability could cause system instability, crashes, or hangs due to deadlocks. It may also lead to memory corruption or privilege escalation if exploited, as it involves improper cleanup of kernel resources.

Compliance Impact

This vulnerability does not directly affect compliance with GDPR, HIPAA, or similar standards. It is a Linux kernel driver issue causing a deadlock and potential use-after-free in the idxd subsystem, which could lead to system instability or crashes. Compliance impacts would only occur if such failures disrupted data processing or security controls, but no evidence suggests this vulnerability enables data breaches or non-compliance.

Mitigation Strategies

Apply the latest kernel update from your distribution to patch the idxd driver flaw. If immediate patching is not possible, disable the idxd driver by blacklisting it or restricting its use via kernel parameters. Monitor system logs for signs of exploitation or instability.

Hi! I’m here to help you understand CVE-2026-74574. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70