dmaengine: idxd: Fix possible invalid memory access after FLR
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.18.216.19.117.0In 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.
From the CVE record · Linux
The Linux kernel’s dmaengine idxd driver can access invalid memory after a Function Level Reset (FLR). This can happen if the first FLR succeeds but the scratch area for saved configuration cannot be allocated during a second FLR. The input does not specify attacker access requirements or user interaction.
Engineers running Linux kernels with the dmaengine idxd driver should check their versions; affected versions are not specified.