leds: mlxreg: Use devm_mutex_init() for mutex initialization
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:
leds: mlxreg: Use devm_mutex_init() for mutex initialization
In this driver LEDs are registered using devm_led_classdev_register() so they are automatically unregistered after module's remove() is done. led_classdev_unregister() calls module's led_set_brightness() to turn off the LEDs and that callback uses mutex which was destroyed already in module's remove() so use devm API instead.
From the CVE record · Linux
The Linux kernel’s mlxreg LED driver can call a brightness callback after its mutex has been destroyed during module removal. The input does not describe an attacker action or specify network access, authentication, or user-interaction requirements.
Engineers running Linux kernels with the mlxreg LED driver should check their versions; affected versions are not specified.