ALSA: hda: Do not unset preset when cleaning up codec
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:
ALSA: hda: Do not unset preset when cleaning up codec
Several functions that take part in codec's initialization and removal are re-used by ASoC codec drivers implementations. Drivers mimic the behavior of hda_codec_driver_probe/remove() found in sound/pci/hda/hda_bind.c with their component->probe/remove() instead.
One of the reasons for that is the expectation of snd_hda_codec_device_new() to receive a valid pointer to an instance of struct snd_card. This expectation can be met only once sound card components probing commences.
As ASoC sound card may be unbound without codec device being actually removed from the system, unsetting ->preset in snd_hda_codec_cleanup_for_unbind() interferes with module unload -> load scenario causing null-ptr-deref. Preset is assigned only once, during device/driver matching whereas ASoC codec driver's module reloading may occur several times throughout the lifetime of an audio stack.
From the CVE record · Linux
The Linux kernel’s ALSA HDA codec cleanup can unset a preset that ASoC codec drivers still need. If an ASoC codec driver module is unloaded and reloaded while the sound card is unbound but the codec device remains, this can cause a null pointer dereference. The input does not establish whether an attacker can trigger this or what access would be required.
Engineers running Linux kernels with ALSA HDA and ASoC codec drivers should check their vendor’s advisory; affected versions are not specified.