[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025022626-CVE-2022-49251-7153@gregkh>
Date: Wed, 26 Feb 2025 02:57:36 +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-49251: ASoC: codecs: va-macro: fix accessing array out of bounds for enum type
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ASoC: codecs: va-macro: fix accessing array out of bounds for enum type
Accessing enums using integer would result in array out of bounds access
on platforms like aarch64 where sizeof(long) is 8 compared to enum size
which is 4 bytes.
The Linux kernel CVE team has assigned CVE-2022-49251 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.11 with commit 908e6b1df26efc9d2df70c9a7bf4f5eae5c5702f and fixed in 5.15.33 with commit 966408e37d84b762d11978b7bfb03fff0c6222ad
Issue introduced in 5.11 with commit 908e6b1df26efc9d2df70c9a7bf4f5eae5c5702f and fixed in 5.16.19 with commit 4a799972a283ab4ec031041304d7e2d34e1a16eb
Issue introduced in 5.11 with commit 908e6b1df26efc9d2df70c9a7bf4f5eae5c5702f and fixed in 5.17.2 with commit c0099bbf8bc85d30c4cf38220fca3c8d4253fa7f
Issue introduced in 5.11 with commit 908e6b1df26efc9d2df70c9a7bf4f5eae5c5702f and fixed in 5.18 with commit 0ea5eff7c6063a8f124188424f8e4c6727f35051
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-49251
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/soc/codecs/lpass-va-macro.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/966408e37d84b762d11978b7bfb03fff0c6222ad
https://git.kernel.org/stable/c/4a799972a283ab4ec031041304d7e2d34e1a16eb
https://git.kernel.org/stable/c/c0099bbf8bc85d30c4cf38220fca3c8d4253fa7f
https://git.kernel.org/stable/c/0ea5eff7c6063a8f124188424f8e4c6727f35051
Powered by blists - more mailing lists