ASoC: SDCA: Fix errors in IRQ cleanup
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:
ASoC: SDCA: Fix errors in IRQ cleanup
IRQs are enabled through sdca_irq_populate() from component probe using devm_request_threaded_irq(), this however means the IRQs can persist if the sound card is torn down. Some of the IRQ handlers store references to the card and the kcontrols which can then fail. Some detail of the crash was explained in [1].
Generally it is not advised to use devm outside of bus probe, so the code is updated to not use devm. The IRQ requests are not moved to bus probe time as it makes passing the snd_soc_component into the IRQs very awkward and would the require a second step once the component is available, so it is simpler to just register the IRQs at this point, even though that necessitates some manual cleanup.
From the CVE record · Linux
In the Linux kernel’s ASoC SDCA code, IRQ handlers can remain registered after a sound card is torn down. If an IRQ occurs afterward, a handler may use stale card or control references and crash. The input does not establish whether an attacker can trigger this, or what access or interaction would be required.
Engineers running Linux kernels with ASoC SDCA support should check their kernel version; affected versions are not specified.