Kernel memory corruption via double device unregister
Published May 1, 2025 · Updated May 11, 2026
Use-after-free in the Linux kernel ASoC core allows local users to corrupt kernel memory during sound module removal. snd_soc_init() ignores failure from snd_soc_util_init(), allowing soc_dummy_dev to be unregistered during failed initialization and again from snd_soc_exit(). Reaching the demonstrated path requires an initialization failure followed by ASoC module removal; the observed result is an invalid kernel-memory read.
Summary
What happened
Use-after-free in the Linux kernel ASoC core allows local users to corrupt kernel memory during sound module removal. snd_soc_init() ignores failure from snd_soc_util_init(), allowing soc_dummy_dev to be unregistered during failed initialization and again from snd_soc_exit(). Reaching the demonstrated path requires an initialization failure followed by ASoC module removal; the observed result is an invalid kernel-memory read.
The record
- CVE
- CVE-2022-49842
- Published
- May 1, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 1, 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=3.0
- Affected versionversion=fb257897bf20c5f0e1df584bb5b874e811651263 <2ec3f558db343b045a7c7419cdbaec266b8ac1a7
- Affected versionversion=fb257897bf20c5f0e1df584bb5b874e811651263 <34eee4189bcebbd5f6a2ff25ef0cb893ad33d51e
- Affected versionversion=fb257897bf20c5f0e1df584bb5b874e811651263 <41fad4f712e081acdfde8b59847f9f66eaf407a0
- Affected versionversion=fb257897bf20c5f0e1df584bb5b874e811651263 <6ec27c53886c8963729885bcf2dd996eba2767a7
- Affected versionversion=fb257897bf20c5f0e1df584bb5b874e811651263 <8d21554ec7680e9585fb852d933203c3db60dad1
- Affected versionversion=fb257897bf20c5f0e1df584bb5b874e811651263 <90bbdf30a51e42378cb23a312005a022794b8e1e
- Affected versionversion=fb257897bf20c5f0e1df584bb5b874e811651263 <a3365e62239dc064019a244bde5686ac18527c22
- Affected versionversion=fb257897bf20c5f0e1df584bb5b874e811651263 <c5674bd073c0fd9f620ca550c5ff08d0d429bdd9
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
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