CVE-2022-50439

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

MEDIUM

5.5

CVSS Score

Published: October 1, 2025 at 11:42 AM UTC

Updated: June 17, 2026 at 05:23 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.2%

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

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

4.2 ≤ v < 5.10.1634.2 ≤ v < 5.15.864.2 ≤ v < 5.4.2294.2 ≤ v < 6.0.164.2 ≤ v < 6.1.24.2 ≤ v < 6.25.11 ≤ v < 5.15.865.16 ≤ v < 6.0.165.5 ≤ v < 5.10.1636.1 ≤ v < 6.1.24.2ee0bcaff109f36d582df9851f204c9a5eb79c028

Vendor states this is fixed in 190685ff4ee03eef8f12c71d8f626e414fa078a9 (fixed)

Vendor states this is fixed in 27e7cf595d4a9fea9d3906b47d0faa87896beeb3 (fixed)

Vendor states this is fixed in 4cbb264d4e9136acab2c8fd39e39ab1b1402b84b (fixed)

Vendor states this is fixed in 57491967ad8f865a9a81d08c36b26facd14d84e5 (fixed)

Vendor states this is fixed in 77c6b6be7e80ca4a4d4b66b63fd5bb48ccefdd5a (fixed)

Vendor states this is fixed in 9ce9c78a2bdbc9a014e7102a35834310c28528b9 (fixed)

Vendor states this is fixed in 4.2 (unaffected)

Vendor states this is fixed in 5.10.163 (unaffected)

Vendor states this is fixed in 5.15.86 (unaffected)

Vendor states this is fixed in 5.4.229 (unaffected)

Vendor states this is fixed in 6.0.16 (unaffected)

Vendor states this is fixed in 6.1.2 (unaffected)