Re: [PATCH 1/2] ASoC: dapm: Fix UAF for snd_soc_pcm_runtime object
From: Mark Brown
Date: Fri Aug 23 2024 - 18:04:06 EST
On Fri, Aug 23, 2024 at 02:43:41PM +0000, Sameer Pujar wrote:
> From: robelin <robelin@xxxxxxxxxx>
>
> When using kernel with the following extra config,
>
> - CONFIG_KASAN=y
> - CONFIG_KASAN_GENERIC=y
> - CONFIG_KASAN_INLINE=y
> - CONFIG_KASAN_VMALLOC=y
> - CONFIG_FRAME_WARN=4096
>
> kernel detects that snd_pcm_suspend_all() access a freed
> 'snd_soc_pcm_runtime' object when the system is suspended, which
> leads to a use-after-free bug:
>
> [ 52.047746] BUG: KASAN: use-after-free in snd_pcm_suspend_all+0x1a8/0x270
> [ 52.047765] Read of size 1 at addr ffff0000b9434d50 by task systemd-sleep/2330
> [ 52.047771]
> [ 52.047776] CPU: 7 PID: 2330 Comm: systemd-sleep Tainted: G O 5.15.148-tegra #9
> [ 52.047781] Hardware name: NVIDIA NVIDIA Jetson AGX Orin Developer Kit/Jetson, BIOS 36.4.0-gcid-36705213 07/01/2024
> [ 52.047785] Call trace:
> [ 52.047787] dump_backtrace+0x0/0x3c0
> [ 52.047794] show_stack+0x34/0x50
Please think hard before including complete backtraces in upstream
reports, they are very large and contain almost no useful information
relative to their size so often obscure the relevant content in your
message. If part of the backtrace is usefully illustrative (it often is
for search engines if nothing else) then it's usually better to pull out
the relevant sections.
Attachment:
signature.asc
Description: PGP signature