backlight: led_bl: Hold led_access lock when calling led_sysfs_disable()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ ae232e45acf9621f2c96b41ca3af006ac7552c33 · < 11d128f7eacec276c75cf4712880a6307ca9c885| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
backlight: led_bl: Hold led_access lock when calling led_sysfs_disable()
Lockdep detects the following issue on led-backlight removal: [ 142.315935] ------------[ cut here ]------------ [ 142.315954] WARNING: CPU: 2 PID: 292 at drivers/leds/led-core.c:455 led_sysfs_enable+0x54/0x80 ... [ 142.500725] Call trace: [ 142.503176] led_sysfs_enable+0x54/0x80 (P) [ 142.507370] led_bl_remove+0x80/0xa8 [led_bl] [ 142.511742] platform_remove+0x30/0x58 [ 142.515501] device_remove+0x54/0x90 ...
Indeed, led_sysfs_enable() has to be called with the led_access lock held.
Hold the lock when calling led_sysfs_disable().
From the CVE record · Linux
The Linux kernel LED backlight removal path calls an LED sysfs function without holding the required led_access lock, triggering a lockdep warning. The input does not establish an attacker action, access requirement, or user interaction needed to trigger the issue.
Engineers running Linux kernels with the LED backlight driver should check whether their kernel includes the fix; affected versions were not provided.