Local information disclosure via LFENCE serialization bypass
Published May 13, 2026 · Updated May 13, 2026
LFENCE serialization failure in affected AMD processors allows local users to disclose sensitive information through speculative execution. The processor does not fully enforce LFENCE as a speculation barrier, allowing execution to proceed transiently past the intended serialization point. Exploitation requires local low-privilege code, high complexity, and specific execution conditions; the reported consequence is confidentiality loss only.
Summary
What happened
LFENCE serialization failure in affected AMD processors allows local users to disclose sensitive information through speculative execution. The processor does not fully enforce LFENCE as a speculation barrier, allowing execution to proceed transiently past the intended serialization point. Exploitation requires local low-privilege code, high complexity, and specific execution conditions; the reported consequence is confidentiality loss only.
The record
- CVE
- CVE-2024-36315
- Published
- May 13, 2026
- Updated
- May 13, 2026
- Vendor
- Advanced Micro Devices, Inc.
- Product
- AMD Ryzen™ 7000 Series Desktop Processors
- Classifications
- CWE-693
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 13, 2026CVE publishedPublication date reported by the CVE source.
- May 13, 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?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
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