ASoC: core: Check for rtd == NULL in snd_soc_remove_pcm_runtime()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 50cd9b5317d5593d0a33f4227f56ddcc1bf66604 · < cecc65827ef3df9754e097582d89569139e6cd1e| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ASoC: core: Check for rtd == NULL in snd_soc_remove_pcm_runtime()
snd_soc_remove_pcm_runtime() might be called with rtd == NULL which will leads to null pointer dereference. This was reproduced with topology loading and marking a link as ignore due to missing hardware component on the system. On module removal the soc_tplg_remove_link() would call snd_soc_remove_pcm_runtime() with rtd == NULL since the link was ignored, no runtime was created.
From the CVE record · Linux
The ASoC core can dereference a null pointer when removing a PCM runtime for a link that was ignored during topology loading because a hardware component was missing. The issue was reproduced during module removal; the input does not describe an attacker path or specify network access, authentication, or user interaction requirements.
Engineers running the Linux kernel with ASoC topology loading should check their systems; affected versions are not specified.