backlight: led-bl: Add devlink to supplier LEDs
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ ae232e45acf9621f2c96b41ca3af006ac7552c33 · < 60a24070392ec726ccfe6ad1ca7b0381c8d8f7c9| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
backlight: led-bl: Add devlink to supplier LEDs
LED Backlight is a consumer of one or multiple LED class devices, but devlink is currently unable to create correct supplier-producer links when the supplier is a class device. It creates instead a link where the supplier is the parent of the expected device.
One consequence is that removal order is not correctly enforced.
Issues happen for example with the following sections in a device tree overlay:
// An LED driver chip pca9632@62 { compatible = "nxp,pca9632"; reg = <0x62>;
// ...
addon_led_pwm: led-pwm@3 { reg = <3>; label = "addon:led:pwm"; }; };
From the CVE record · Linux
The Linux kernel's LED backlight driver can link to the wrong supplier device, leaving device removal order unenforced. Removing an affected device-tree overlay or locally unbinding the supplying LED device before the backlight device can cause a kernel NULL pointer dereference; the input does not specify authentication requirements.
Engineers running Linux kernels with LED backlight devices supplied by LED class devices should check their systems; affected versions are not specified.