Service interruption via unreleased AC'97 device name
Published Oct 1, 2025 · Updated Oct 1, 2025
Memory leak in Linux kernel ALSA AC'97 support allows local users to deplete kernel memory when AC'97 device registration fails. snd_ac97_dev_register() calls device_register() after dev_set_name() allocates a device name, but the failure path omits put_device() and retains that allocation. Reachability requires a registration failure in the AC'97 path; repeated reachable failures can exhaust memory and interrupt service.
Summary
What happened
Memory leak in Linux kernel ALSA AC'97 support allows local users to deplete kernel memory when AC'97 device registration fails. snd_ac97_dev_register() calls device_register() after dev_set_name() allocates a device name, but the failure path omits put_device() and retains that allocation. Reachability requires a registration failure in the AC'97 path; repeated reachable failures can exhaust memory and interrupt service.
The record
- CVE
- CVE-2022-50427
- Published
- Oct 1, 2025
- Updated
- Oct 1, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-401
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 1, 2025CVE publishedPublication date reported by the CVE source.
- Oct 1, 2025Record 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=0ca06a00e206b963587ac471e6d1c52bf33b9a18 <0f8e9a15c8ecf95057061d370a2dddaf1cee4aeb
- Affected versionversion=0ca06a00e206b963587ac471e6d1c52bf33b9a18 <4881bda5ea05c8c240fc8afeaa928e2bc43f61fa
- Affected versionversion=0ca06a00e206b963587ac471e6d1c52bf33b9a18 <4fdf6f978c6b605ca0d67bf0e982b7a8fc0f4aab
- Affected versionversion=0ca06a00e206b963587ac471e6d1c52bf33b9a18 <758dbcc6fbf2286eff02743b093c70a18a407d66
- Affected versionversion=0ca06a00e206b963587ac471e6d1c52bf33b9a18 <a602ec9d88f177dba78bc97fb1adecc7a71ff279
- Affected versionversion=0ca06a00e206b963587ac471e6d1c52bf33b9a18 <bfce73088682ef0770da951f51156c36a89be490
- Affected versionversion=0ca06a00e206b963587ac471e6d1c52bf33b9a18 <c68b2e9ef246117f696e360bbdd2f5736b3a7127
- Affected versionversion=0ca06a00e206b963587ac471e6d1c52bf33b9a18 <ee8bf0946f62ef00e5db4b613a9f664ac567259a
- Affected versionversion=2.6.14
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