Local privilege escalation via permissive installation directory
Published May 13, 2025 · Updated Feb 26, 2026
Incorrect permissions in AMD Optimizing CPU Libraries before 4.2.1 allow local users to escalate privileges and execute arbitrary code. The installer assigns overly permissive default access controls to the AOCL installation directory; AMD has not disclosed the affected path, files, or privileged load operation. Exploitation requires local low privileges and user interaction, and successful exploitation executes code with elevated privileges.
Summary
What happened
Incorrect permissions in AMD Optimizing CPU Libraries before 4.2.1 allow local users to escalate privileges and execute arbitrary code. The installer assigns overly permissive default access controls to the AOCL installation directory; AMD has not disclosed the affected path, files, or privileged load operation. Exploitation requires local low privileges and user interaction, and successful exploitation executes code with elevated privileges.
The record
- CVE
- CVE-2024-21960
- Published
- May 13, 2025
- Updated
- Feb 26, 2026
- Vendor
- Advanced Micro Devices, Inc.
- Product
- AMD Optimizing CPU Libraries (AOCL)
- Classifications
- CWE-276, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 13, 2025CVE publishedPublication date reported by the CVE source.
- Feb 26, 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