Kernel panic via unlocked regmap synchronization
Published Feb 5, 2024 · Updated Aug 1, 2024
Race condition in Linux Kernel 5.6-rc1 through 6.4 allows local users to panic the kernel through HDA runtime-resume activity. snd_hdac_regmap_sync checks codec->regmap and calls regcache_sync without holding regmap_lock, allowing a concurrent NULL assignment between the check and dereference. The race requires local low-privileged access, specific concurrent timing, and HDA runtime-resume activity; a successful trigger interrupts the host by panicking the kernel.
Summary
What happened
Race condition in Linux Kernel 5.6-rc1 through 6.4 allows local users to panic the kernel through HDA runtime-resume activity. snd_hdac_regmap_sync checks codec->regmap and calls regcache_sync without holding regmap_lock, allowing a concurrent NULL assignment between the check and dereference. The race requires local low-privileged access, specific concurrent timing, and HDA runtime-resume activity; a successful trigger interrupts the host by panicking the kernel.
The record
- CVE
- CVE-2024-23196
- Published
- Feb 5, 2024
- Updated
- Aug 1, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-476, CWE-362, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 5, 2024CVE publishedPublication date reported by the CVE source.
- Aug 1, 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=v5.6-rc1 <v6.5-rc1
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.
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