Kernel crash via misordered ALSA name bounds check
Published Sep 13, 2022 · Updated Aug 3, 2024
Out-of-bounds read in Linux Kernel before 6.0-rc4 allows local users with elevated privileges to crash the system through an ioctl. The ALSA get_ctl_id_hash loop tests a name byte before confirming that the offset remains below the fixed array bound when no null terminator is present. The ioctl path requires privileged local access; the source does not establish whether the one-byte overread reliably escalates privileges beyond the demonstrated crash.
Summary
What happened
Out-of-bounds read in Linux Kernel before 6.0-rc4 allows local users with elevated privileges to crash the system through an ioctl. The ALSA get_ctl_id_hash loop tests a name byte before confirming that the offset remains below the fixed array bound when no null terminator is present. The ioctl path requires privileged local access; the source does not establish whether the one-byte overread reliably escalates privileges beyond the demonstrated crash.
The record
- CVE
- CVE-2022-3170
- Published
- Sep 13, 2022
- Updated
- Aug 3, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-125, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 13, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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=fixed in kernel 6.0-rc4
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