Service interruption via leaked device-tree reference
Published Feb 26, 2025 · Updated May 11, 2026
Resource leak in the MediaTek MT8173 MAX98090 ASoC driver allows local users to interrupt service through the device probe path. mt8173_max98090_dev_probe returns an error for a missing or invalid audio-codec property without releasing platform_node, retaining a device-tree node reference. The affected driver and malformed device-tree condition must be present; published sources do not describe how local users trigger repeated probe failures.
Summary
What happened
Resource leak in the MediaTek MT8173 MAX98090 ASoC driver allows local users to interrupt service through the device probe path. mt8173_max98090_dev_probe returns an error for a missing or invalid audio-codec property without releasing platform_node, retaining a device-tree node reference. The affected driver and malformed device-tree condition must be present; published sources do not describe how local users trigger repeated probe failures.
The record
- CVE
- CVE-2022-49514
- Published
- Feb 26, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 26, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.2
- Affected versionversion=94319ba10ecabc8f28129566d1f5793e3e7a0a79 <0a1901f34f775b83ea4b8dbb5ed992147b9b8531
- Affected versionversion=94319ba10ecabc8f28129566d1f5793e3e7a0a79 <1e932aba3c7628c9f880ee9c2cfcc2ae3ba0c01e
- Affected versionversion=94319ba10ecabc8f28129566d1f5793e3e7a0a79 <23f340ed906c758cec6527376768e3bc1474ac30
- Affected versionversion=94319ba10ecabc8f28129566d1f5793e3e7a0a79 <48889eb3cce91d7f58e02bc07277b7f724b7a54a
- Affected versionversion=94319ba10ecabc8f28129566d1f5793e3e7a0a79 <4f4e0454e226de3bf4efd7e7924d1edc571c52d5
- Affected versionversion=94319ba10ecabc8f28129566d1f5793e3e7a0a79 <98d5afe868df998b0244f4c229ab758b4083684a
- Affected versionversion=94319ba10ecabc8f28129566d1f5793e3e7a0a79 <cc43b9fdca519c5b13be6a717bacbebccd628cf6
- Affected versionversion=94319ba10ecabc8f28129566d1f5793e3e7a0a79 <ebd5cb4f1f3f10b839e7575219e0f17b60c23113
- Affected versionversion=94319ba10ecabc8f28129566d1f5793e3e7a0a79 <fb66e0512e5ccc093070e21cf88cce8d98c181b5
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo