Kernel memory corruption via double device release
Published May 17, 2024 · Updated May 11, 2026
A double device release in Linux kernel 6.5 ASoC Intel board code allows local users to corrupt kernel memory during codec teardown. The sof_sdw_rt_sdca_jack_exit() path calls put_device() twice because mc_dailink_exit_loop() invokes the shared exit handler for codecs with the same DAI name without clearing ctx->headset_codec_dev after the first release. Reachability requires affected Intel SoundWire audio hardware with codecs such as RT712 and RT713 sharing the rt712-sdca-aif1 name; the stale device reference can corrupt kernel state or interrupt the system.
Summary
What happened
A double device release in Linux kernel 6.5 ASoC Intel board code allows local users to corrupt kernel memory during codec teardown. The sof_sdw_rt_sdca_jack_exit() path calls put_device() twice because mc_dailink_exit_loop() invokes the shared exit handler for codecs with the same DAI name without clearing ctx->headset_codec_dev after the first release. Reachability requires affected Intel SoundWire audio hardware with codecs such as RT712 and RT713 sharing the rt712-sdca-aif1 name; the stale device reference can corrupt kernel state or interrupt the system.
The record
- CVE
- CVE-2023-52697
- Published
- May 17, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 17, 2024CVE 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=5360c67046385f90406ec17e367ba9aeb42d5459 <582231a8c4f73ac153493687ecc1bed853e9c9ef
- Affected versionversion=5360c67046385f90406ec17e367ba9aeb42d5459 <a410d58117d6da4b7d41f3c91365f191d006bc3d
- Affected versionversion=5360c67046385f90406ec17e367ba9aeb42d5459 <e38e252dbceeef7d2f848017132efd68e9ae1416
- Affected versionversion=6.5
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