Local information disclosure via uninitialized DXE pointer
Published Sep 20, 2023 · Updated Jun 27, 2025
Improper initialization in affected AMD Ryzen processor DXE drivers allows local users with high privileges to disclose firmware memory. The driver accesses an uninitialized pointer, allowing adjacent firmware memory to be returned through a locally reachable privileged interface. AMD reports confidentiality loss only, and the affected interface and disclosed data have not been published.
Summary
What happened
Improper initialization in affected AMD Ryzen processor DXE drivers allows local users with high privileges to disclose firmware memory. The driver accesses an uninitialized pointer, allowing adjacent firmware memory to be returned through a locally reachable privileged interface. AMD reports confidentiality loss only, and the affected interface and disclosed data have not been published.
The record
- CVE
- CVE-2023-20594
- Published
- Sep 20, 2023
- Updated
- Jun 27, 2025
- Vendor
- AMD
- Product
- Ryzen 5000 Series Mobile Processors with Radeon Graphics (Lucienne)
- Classifications
- CWE-824, CWE-665
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Sep 20, 2023CVE publishedPublication date reported by the CVE source.
- Jun 27, 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=various
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.
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