dmaengine: idxd: Avoid unnecessary destruction of file_ida
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.6.336.9.46.10In the Linux kernel, the following vulnerability has been resolved:
dmaengine: idxd: Avoid unnecessary destruction of file_ida
file_ida is allocated during cdev open and is freed accordingly during cdev release. This sequence is guaranteed by driver file operations. Therefore, there is no need to destroy an already empty file_ida when the WQ cdev is removed.
Worse, ida_free() in cdev release may happen after destruction of file_ida per WQ cdev. This can lead to accessing an id in file_ida after it has been destroyed, resulting in a kernel panic.
Remove ida_destroy(&file_ida) to address these issues.
From the CVE record · Linux
The Linux kernel's dmaengine idxd driver can access a destroyed file_ida if cdev release occurs after WQ cdev removal, causing a kernel panic. The input does not specify how an attacker could trigger this condition, whether authentication is needed, or whether user interaction is required.
Engineers running Linux kernels with the dmaengine idxd driver should check their systems; affected versions are not specified.