linux-cve-announce - CVE-2022-50439: ASoC: mediatek: mt8173: Enable IRQ when pdata is ready

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025100100-CVE-2022-50439-6054@gregkh>
Date: Wed,  1 Oct 2025 13:42:12 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-50439: ASoC: mediatek: mt8173: Enable IRQ when pdata is ready

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

ASoC: mediatek: mt8173: Enable IRQ when pdata is ready

If the device does not come straight from reset, we might receive an IRQ
before we are ready to handle it.


[    2.334737] Unable to handle kernel read from unreadable memory at virtual address 00000000000001e4
[    2.522601] Call trace:
[    2.525040]  regmap_read+0x1c/0x80
[    2.528434]  mt8173_afe_irq_handler+0x40/0xf0
...
[    2.598921]  start_kernel+0x338/0x42c

The Linux kernel CVE team has assigned CVE-2022-50439 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 4.2 with commit ee0bcaff109f36d582df9851f204c9a5eb79c028 and fixed in 5.4.229 with commit 190685ff4ee03eef8f12c71d8f626e414fa078a9
	Issue introduced in 4.2 with commit ee0bcaff109f36d582df9851f204c9a5eb79c028 and fixed in 5.10.163 with commit 57491967ad8f865a9a81d08c36b26facd14d84e5
	Issue introduced in 4.2 with commit ee0bcaff109f36d582df9851f204c9a5eb79c028 and fixed in 5.15.86 with commit 27e7cf595d4a9fea9d3906b47d0faa87896beeb3
	Issue introduced in 4.2 with commit ee0bcaff109f36d582df9851f204c9a5eb79c028 and fixed in 6.0.16 with commit 9ce9c78a2bdbc9a014e7102a35834310c28528b9
	Issue introduced in 4.2 with commit ee0bcaff109f36d582df9851f204c9a5eb79c028 and fixed in 6.1.2 with commit 77c6b6be7e80ca4a4d4b66b63fd5bb48ccefdd5a
	Issue introduced in 4.2 with commit ee0bcaff109f36d582df9851f204c9a5eb79c028 and fixed in 6.2 with commit 4cbb264d4e9136acab2c8fd39e39ab1b1402b84b

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-50439
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/mediatek/mt8173/mt8173-afe-pcm.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/190685ff4ee03eef8f12c71d8f626e414fa078a9
	https://git.kernel.org/stable/c/57491967ad8f865a9a81d08c36b26facd14d84e5
	https://git.kernel.org/stable/c/27e7cf595d4a9fea9d3906b47d0faa87896beeb3
	https://git.kernel.org/stable/c/9ce9c78a2bdbc9a014e7102a35834310c28528b9
	https://git.kernel.org/stable/c/77c6b6be7e80ca4a4d4b66b63fd5bb48ccefdd5a
	https://git.kernel.org/stable/c/4cbb264d4e9136acab2c8fd39e39ab1b1402b84b