CVE-2026-31442
Received Received - Intake
Use-After-Free in Linux dmaengine idxd After FLR

Publication date: 2026-04-22

Last updated on: 2026-04-27

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: Fix possible invalid memory access after FLR In the case that the first Function Level Reset (FLR) concludes correctly, but in the second FLR the scratch area for the saved configuration cannot be allocated, it's possible for a invalid memory access to happen. Always set the deallocated scratch area to NULL after FLR completes.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-04-22
Last Modified
2026-04-27
Generated
2026-05-07
AI Q&A
2026-04-22
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
What immediate steps should I take to mitigate this vulnerability?

To mitigate this vulnerability, ensure that your Linux kernel is updated to a version where the dmaengine idxd driver has the fix applied. This fix addresses the invalid memory access issue after Function Level Reset (FLR) by properly handling the scratch area allocation and setting it to NULL after FLR completes.

Applying the latest kernel patches or upgrading to a fixed kernel version is the recommended immediate step.


How can this vulnerability impact me? :

An invalid memory access vulnerability can lead to system instability, crashes, or potential security risks such as privilege escalation or denial of service. In this case, if the scratch area is not properly handled after a Function Level Reset, it could cause the Linux kernel to access invalid memory, potentially affecting system reliability and security.


Can you explain this vulnerability to me?

This vulnerability exists in the Linux kernel's dmaengine idxd component. It involves a potential invalid memory access that can occur after a Function Level Reset (FLR). Specifically, if the first FLR completes successfully but the second FLR fails to allocate the scratch area for the saved configuration, an invalid memory access may happen. The fix involves always setting the deallocated scratch area to NULL after the FLR completes to prevent this issue.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart