thermal/debugfs: Prevent use-after-free from occurring after cdev removal
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 |
|
|
In the Linux kernel, the following vulnerability has been resolved:
thermal/debugfs: Prevent use-after-free from occurring after cdev removal
Since thermal_debug_cdev_remove() does not run under cdev->lock, it can run in parallel with thermal_debug_cdev_state_update() and it may free the struct thermal_debugfs object used by the latter after it has been checked against NULL.
If that happens, thermal_debug_cdev_state_update() will access memory that has been freed already causing the kernel to crash.
Address this by using cdev->lock in thermal_debug_cdev_remove() around the cdev->debugfs value check (in case the same cdev is removed at the same time in two different threads) and its reset to NULL.
Cc :6.8+ <stable@vger.kernel.org> # 6.8+
From the CVE record · Linux
A race between cooling-device removal and state updates in Linux kernel thermal/debugfs can cause a use-after-free and crash the kernel. It requires those operations to run concurrently; the input does not specify attacker access or authentication requirements.
Teams running Linux kernels in the 6.8+ stable series should check whether their builds include the fix.