From: Jaroslav Kysela <perex@perex.cz>
To: Takashi Iwai <tiwai@suse.de>, Greg KH <gregkh@linuxfoundation.org>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, Clement Lecigne <clecigne@google.com>
Subject: Re: [PATCH 5.10.y] ALSA: pcm: Properly take rwsem lock in ctl_elem_read_user/ctl_elem_write_user to prevent UAF
Date: Fri, 13 Jan 2023 15:45:27 +0100 [thread overview]
Message-ID: <e0dae3a0-4176-0bc7-42e4-65cf58f265ad@perex.cz> (raw)
In-Reply-To: <20230113142639.4420-1-tiwai@suse.de>
On 13. 01. 23 15:26, Takashi Iwai wrote:
> From: Clement Lecigne <clecigne@google.com>
>
> [ Note: this is a fix that works around the bug equivalently as the
> two upstream commits:
> 1fa4445f9adf ("ALSA: control - introduce snd_ctl_notify_one() helper")
> 56b88b50565c ("ALSA: pcm: Move rwsem lock inside snd_ctl_elem_read to prevent UAF")
> but in a simpler way to fit with older stable trees -- tiwai ]
>
> Add missing locking in ctl_elem_read_user/ctl_elem_write_user which can be
> easily triggered and turned into an use-after-free.
>
> Example code paths with SNDRV_CTL_IOCTL_ELEM_READ:
>
> 64-bits:
> snd_ctl_ioctl
> snd_ctl_elem_read_user
> [takes controls_rwsem]
> snd_ctl_elem_read [lock properly held, all good]
> [drops controls_rwsem]
>
> 32-bits (compat):
> snd_ctl_ioctl_compat
> snd_ctl_elem_write_read_compat
> ctl_elem_write_read
> snd_ctl_elem_read [missing lock, not good]
>
> CVE-2023-0266 was assigned for this issue.
>
> Signed-off-by: Clement Lecigne <clecigne@google.com>
> Cc: stable@kernel.org # 5.12 and older
> Signed-off-by: Takashi Iwai <tiwai@suse.de>
Reviewed-by: Jaroslav Kysela <perex@perex.cz>
--
Jaroslav Kysela <perex@perex.cz>
Linux Sound Maintainer; ALSA Project; Red Hat, Inc.
next prev parent reply other threads:[~2023-01-13 14:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 14:26 Takashi Iwai
2023-01-13 14:45 ` Jaroslav Kysela [this message]
2023-01-13 15:43 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e0dae3a0-4176-0bc7-42e4-65cf58f265ad@perex.cz \
--to=perex@perex.cz \
--cc=alsa-devel@alsa-project.org \
--cc=clecigne@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tiwai@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®