[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025022633-CVE-2022-49288-d3cb@gregkh>
Date: Wed, 26 Feb 2025 02:58:13 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2022-49288: ALSA: pcm: Fix races among concurrent prealloc proc writes
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ALSA: pcm: Fix races among concurrent prealloc proc writes
We have no protection against concurrent PCM buffer preallocation
changes via proc files, and it may potentially lead to UAF or some
weird problem. This patch applies the PCM open_mutex to the proc
write operation for avoiding the racy proc writes and the PCM stream
open (and further operations).
The Linux kernel CVE team has assigned CVE-2022-49288 to this issue.
Affected and fixed versions
===========================
Fixed in 4.14.279 with commit e7786c445bb67a9a6e64f66ebd6b7215b153ff7d
Fixed in 4.19.243 with commit e14dca613e0a6ddc2bf6e360f16936a9f865205b
Fixed in 5.4.193 with commit 37b12c16beb6f6c1c3c678c1aacbc46525c250f7
Fixed in 5.10.109 with commit b560d670c87d7d40b3cf6949246fa4c7aa65a00a
Fixed in 5.15.32 with commit 51fce708ab8986a9879ee5da946a2cc120f1036d
Fixed in 5.16.18 with commit a21d2f323b5a978dedf9ff1d50f101f85e39b3f2
Fixed in 5.17.1 with commit 5ed8f8e3c4e59d0396b9ccf2e639711e24295bb6
Fixed in 5.18 with commit 69534c48ba8ce552ce383b3dfdb271ffe51820c3
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2022-49288
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
sound/core/pcm_memory.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/e7786c445bb67a9a6e64f66ebd6b7215b153ff7d
https://git.kernel.org/stable/c/e14dca613e0a6ddc2bf6e360f16936a9f865205b
https://git.kernel.org/stable/c/37b12c16beb6f6c1c3c678c1aacbc46525c250f7
https://git.kernel.org/stable/c/b560d670c87d7d40b3cf6949246fa4c7aa65a00a
https://git.kernel.org/stable/c/51fce708ab8986a9879ee5da946a2cc120f1036d
https://git.kernel.org/stable/c/a21d2f323b5a978dedf9ff1d50f101f85e39b3f2
https://git.kernel.org/stable/c/5ed8f8e3c4e59d0396b9ccf2e639711e24295bb6
https://git.kernel.org/stable/c/69534c48ba8ce552ce383b3dfdb271ffe51820c3
Powered by blists - more mailing lists