net/dibs: Correct freeing of dmb_clientid_arr
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.457.1.97.2In the Linux kernel, the following vulnerability has been resolved:
net/dibs: Correct freeing of dmb_clientid_arr
A dibs device interrupt handler can be active after dibs_dev_del() and may still access dmb_clientid_arr. (UAF)
In case of a failure in dibs_dev_add() being called by dibs_lo_dev_probe() dmb_clientid_arr is freed twice (double free).
Free dmb_clientid_arr in dibs_dev_release() after last reference is gone. Note that allocating in dibs_dev_add() instead of dibs_dev_alloc() is ok for now, because no dmbs can be registered before dibs_dev_add().
From the CVE record · Linux
The Linux kernel's net/dibs code can access dmb_clientid_arr after it is freed if a device interrupt handler remains active after dibs_dev_del(). A failure in dibs_dev_add() during dibs_lo_dev_probe() can also free the array twice. The input does not specify attacker access requirements or user interaction.
Engineers running Linux kernels with the affected net/dibs code should check their versions; affected versions are not specified.