ALSA: control: Don't add invalid kcontrols to LED layer
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 22d8de62f11b287b279f1d4473a78c7d5e53e7bc · < 74e3b979ce8b78a690f8b94ccf2e2c965f7f5c11| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ALSA: control: Don't add invalid kcontrols to LED layer
The kcontrol LED state layer tries to track the all associated kcontrol elements with naive assumptions that they are readable. But one can create a write-only element that has no get callback (even a user element can do it), and this may lead to a NULL dereference at the call chain of snd_ctl_led_notify(), as found by syzkaller.
For avoiding the Oops, add a sanity check of the kcontrol's info and get callbacks, and just skip the invalid kcontrols before assigning the kctl to the LED layer.
From the CVE record · Linux
The ALSA control LED layer may attempt to read a write-only control element with no get callback. Someone able to create such an element, including a user element, may trigger a kernel NULL dereference. The input does not specify authentication requirements or whether further user interaction is needed.
Teams running the Linux kernel should check their systems; affected versions are not specified.