Local kernel memory corruption via vtpmx race
Published Dec 30, 2025 · Updated Dec 30, 2025
Race condition in the vtpm proxy in Linux allows local users to corrupt kernel memory by racing /dev/vtpmx device creation. The driver registers the misc device before its workqueue is initialized, so an immediate open can reach a partially initialized proxy object. Exploitation requires low-privileged local access and high-complexity timing; the documented consequence is kernel-memory corruption that can damage integrity or interrupt the host.
Summary
What happened
Race condition in the vtpm proxy in Linux allows local users to corrupt kernel memory by racing /dev/vtpmx device creation. The driver registers the misc device before its workqueue is initialized, so an immediate open can reach a partially initialized proxy object. Exploitation requires low-privileged local access and high-complexity timing; the documented consequence is kernel-memory corruption that can damage integrity or interrupt the host.
The record
- CVE
- CVE-2023-54309
- Published
- Dec 30, 2025
- Updated
- Dec 30, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 30, 2025CVE publishedPublication date reported by the CVE source.
- Dec 30, 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=4.8
- Affected versionversion=6f99612e250041a2402d3b1694bccb149cd424a4 <04e8697d26613ccea760cf57eb20a5a27f788c0f
- Affected versionversion=6f99612e250041a2402d3b1694bccb149cd424a4 <092db954e2c3c5ba6c0ce990c7da72cf8f3b9c51
- Affected versionversion=6f99612e250041a2402d3b1694bccb149cd424a4 <509d21f1c4bb9d35d397fca3226165b156a7639f
- Affected versionversion=6f99612e250041a2402d3b1694bccb149cd424a4 <86b9820395f226b8f33cbae9599deebf8af1ce72
- Affected versionversion=6f99612e250041a2402d3b1694bccb149cd424a4 <99b998fb9d7d2d2d9dbb3e19db2d0ade02f5a604
- Affected versionversion=6f99612e250041a2402d3b1694bccb149cd424a4 <9ff7fcb3a2ed0e9b895bb5b4c13872d584a8815b
- Affected versionversion=6f99612e250041a2402d3b1694bccb149cd424a4 <e08295290c53a3cf174c236721747a01b9550ae2
- Affected versionversion=6f99612e250041a2402d3b1694bccb149cd424a4 <f4032d615f90970d6c3ac1d9c0bce3351eb4445c
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