Revert "hwmon: (ibmpex) fix use-after-free in high/low store"
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 6946c726c3f4c36f0f049e6f97e88c510b15f65d · < 894d9c7aab68fd0c70c78b1d03c8fa589fb0f67d| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
Revert "hwmon: (ibmpex) fix use-after-free in high/low store"
This reverts commit 6946c726c3f4c36f0f049e6f97e88c510b15f65d.
Jean Delvare points out that the patch does not completely fix the reported problem, that it in fact introduces a (new) race condition, and that it may actually not be needed in the first place.
Various AI reviews agree. Specific and relevant AI feedback:
" This reordering sets the driver data to NULL before removing the sensor attributes in the loop below.
ibmpex_show_sensor() retrieves this driver data via dev_get_drvdata() but does not check if it is NULL before dereferencing it to access data->sensors[].
If a userspace process reads a sensor file (like temp1_input) while this delete function is running, could it race with the dev_set_drvdata(..., NULL) call here and crash in ibmpex_show_sensor()?
From the CVE record · Linux
The Linux kernel’s ibmpex hardware-monitoring driver has a race condition in its sensor-file handling. A local userspace process reading a sensor file while the driver removes sensor attributes could trigger a kernel crash; the input does not specify whether authentication is required.
Teams running Linux kernels with the ibmpex hardware-monitoring driver should check their kernel builds; affected versions are not specified.