Privileged kernel-memory disclosure via untrusted syscall pointer
Published Feb 10, 2026 · Updated Feb 10, 2026
Untrusted pointer dereference in AMD Secure Processor firmware allows local users with high privileges to infer kernel-memory contents. The ASP syscall input path accepts an untrusted pointer without validating its target and causes the kernel to read parameters from kernel memory. Exploitation requires local high-privilege access and high-complexity conditions; the bounded consequence is indirect disclosure of kernel contents.
Summary
What happened
Untrusted pointer dereference in AMD Secure Processor firmware allows local users with high privileges to infer kernel-memory contents. The ASP syscall input path accepts an untrusted pointer without validating its target and causes the kernel to read parameters from kernel memory. Exploitation requires local high-privilege access and high-complexity conditions; the bounded consequence is indirect disclosure of kernel contents.
The record
- CVE
- CVE-2021-26410
- Published
- Feb 10, 2026
- Updated
- Feb 10, 2026
- Vendor
- Advanced Micro Devices, Inc.
- Product
- AMD Ryzen™ Embedded V1000 Series Processors
- Classifications
- CWE-822
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Feb 10, 2026CVE publishedPublication date reported by the CVE source.
- Feb 10, 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