Local memory corruption via stale WMI device pointer
Published May 21, 2024 · Updated Aug 5, 2026
Memory corruption in the Linux kernel WMI character-device interface allows local users to corrupt kernel memory during device removal. wmi_char_open treats filp->private_data as WMI device data even though the miscdevice layer stores a miscdevice pointer there, so driver lookup can fail or select a same-named device. Reaching the flaw requires local access to the WMI character device while its associated WMI device is deleted; the reported consequence is kernel-memory corruption.
Summary
What happened
Memory corruption in the Linux kernel WMI character-device interface allows local users to corrupt kernel memory during device removal. wmi_char_open treats filp->private_data as WMI device data even though the miscdevice layer stores a miscdevice pointer there, so driver lookup can fail or select a same-named device. Reaching the flaw requires local access to the WMI character device while its associated WMI device is deleted; the reported consequence is kernel-memory corruption.
The record
- CVE
- CVE-2023-52864
- Published
- May 21, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-787
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 21, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=4.15
- Affected versionversion=44b6b7661132b1b0e5fd3147ded66f1e4a817ca9 <36d85fa7ae0d6be651c1a745191fa7ef055db43e
- Affected versionversion=44b6b7661132b1b0e5fd3147ded66f1e4a817ca9 <44a96796d25809502c75771d40ee693c2e44724e
- Affected versionversion=44b6b7661132b1b0e5fd3147ded66f1e4a817ca9 <9fb0eed09e1470cd4021ff52b2b9dfcbcee4c203
- Affected versionversion=44b6b7661132b1b0e5fd3147ded66f1e4a817ca9 <cf098e937dd125c0317a0d6f261ac2a950a233d6
- Affected versionversion=44b6b7661132b1b0e5fd3147ded66f1e4a817ca9 <d426a2955e45a95b2282764105fcfb110a540453
- Affected versionversion=44b6b7661132b1b0e5fd3147ded66f1e4a817ca9 <e0bf076b734a2fab92d8fddc2b8b03462eee7097
- Affected versionversion=44b6b7661132b1b0e5fd3147ded66f1e4a817ca9 <eba9ac7abab91c8f6d351460239108bef5e7a0b6
- Affected versionversion=44b6b7661132b1b0e5fd3147ded66f1e4a817ca9 <fb7b06b59c6887659c6ed0ecd3110835eecbb6a3
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