CVE-2024-46798: ASoC: dapm: Fix UAF for snd_soc_pcm_runtime object
ASoC: dapm: Fix UAF for sndsocpcmruntime object
Other sources
This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.
— Launchpad
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.133-1Fixed in 6.12.22-1 - Upgrade
Upgrade
debian/linux-6.1to a version that resolves this vulnerability.Fixed in 6.1.129-1~deb11u1 - Configuration
If building with CONFIG_KASAN=y, CONFIG_KASAN_GENERIC=y, CONFIG_KASAN_INLINE=y, CONFIG_KASAN_VMALLOC=y, and CONFIG_FRAME_WARN=4096, ensure the ASoC dapm fix for the UAF in snd_pcm_suspend_all() is applied so suspending does not access a freed snd_soc_pcm_runtime object.
Linux kernel (ALSA ASoC dapm) CONFIG_KASAN = y - Configuration
Apply the code change described: always set 'substream->runtime' to NULL every time the kernel kfree()s it, so that snd_pcm_sync_stop() (which has a NULL check) and snd_pcm_suspend_all() do not access a freed 'snd_soc_pcm_runtime' object during system suspend.
Linux kernel (ALSA ASoC dapm) snd_pcm_runtime lifetime handling = set substream->runtime to NULL after kfree
Event History
Frequently Asked Questions
What is the severity of CVE-2024-46798?
CVE-2024-46798 has a medium severity rating due to a use-after-free vulnerability in the Linux kernel.
How does CVE-2024-46798 affect system security?
CVE-2024-46798 can allow an attacker to execute arbitrary code, potentially leading to system compromise.
How do I fix CVE-2024-46798?
To fix CVE-2024-46798, update your Linux kernel to the recommended patched versions such as 5.10.226-1 or 6.1.123-1.
Which systems are affected by CVE-2024-46798?
CVE-2024-46798 affects various versions of the Linux kernel, including configurations with KASAN enabled.
What is the impact of not addressing CVE-2024-46798?
Not addressing CVE-2024-46798 could leave your system vulnerable to exploitation and potential data breaches.