[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025022626-CVE-2022-49252-f276@gregkh>
Date: Wed, 26 Feb 2025 02:57:37 +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-49252: ASoC: codecs: rx-macro: fix accessing array out of bounds for enum type
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ASoC: codecs: rx-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-49252 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.12 with commit 4f692926f562ff48abfcca6b16f36ff8d57473b6 and fixed in 5.15.33 with commit eb15c6ea692fd88d70698d874d9a0d667fb4cde9
Issue introduced in 5.12 with commit 4f692926f562ff48abfcca6b16f36ff8d57473b6 and fixed in 5.16.19 with commit 7e3629e256d1cabf801d00050550ade4d036cafe
Issue introduced in 5.12 with commit 4f692926f562ff48abfcca6b16f36ff8d57473b6 and fixed in 5.17.2 with commit aed43e92e4b9187029903880d5db608f7fa1c53c
Issue introduced in 5.12 with commit 4f692926f562ff48abfcca6b16f36ff8d57473b6 and fixed in 5.18 with commit bcfe5f76cc4051ea3f9eb5d2c8ea621641f290a5
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-49252
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-rx-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/eb15c6ea692fd88d70698d874d9a0d667fb4cde9
https://git.kernel.org/stable/c/7e3629e256d1cabf801d00050550ade4d036cafe
https://git.kernel.org/stable/c/aed43e92e4b9187029903880d5db608f7fa1c53c
https://git.kernel.org/stable/c/bcfe5f76cc4051ea3f9eb5d2c8ea621641f290a5
Powered by blists - more mailing lists