How severe is CVE-2021-26410?

CVE-2021-26410 has a CVSS 4.0 base score of 1.8, rated low severity.

Is CVE-2021-26410 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (4th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2021-26410?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2021-26410 have an EU (EUVD) identifier?

Yes. CVE-2021-26410 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2021-13216.

When was CVE-2021-26410 published?

CVE-2021-26410 was published on 2026-02-10 and last updated on 2026-06-17.

CVE-2021-26410

CVE-2021-26410 is a low-severity vulnerability with a CVSS 4.0 base score of 1.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-822.

Key facts

Severity: Low (CVSS 4.0 base score 1.8)
EPSS exploit prediction: 0% (4th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2021-13216
Weakness: CWE-822
Published: 2026-02-10
Last modified: 2026-06-17

Description

Improper syscall input validation in ASP (AMD Secure Processor) may force the kernel into reading syscall parameter values from its own memory space allowing an attacker to infer the contents of the kernel memory leading to potential information disclosure.

Frequently asked questions

What is CVE-2021-26410?: Improper syscall input validation in ASP (AMD Secure Processor) may force the kernel into reading syscall parameter values from its own memory space allowing an attacker to infer the contents of the kernel memory leading to potential information disclosure.
How severe is CVE-2021-26410?: CVE-2021-26410 has a CVSS 4.0 base score of 1.8, rated low severity.
Is CVE-2021-26410 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (4th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2021-26410?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2021-26410 have an EU (EUVD) identifier?: Yes. CVE-2021-26410 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2021-13216.
When was CVE-2021-26410 published?: CVE-2021-26410 was published on 2026-02-10 and last updated on 2026-06-17.

References

Other CWE-822 vulnerabilities

CVE-2025-50165 — Critical (CVSS 9.8): Untrusted pointer dereference in Microsoft Graphics Component allows an unauthorized attacker to execute code over a…
CVE-2023-1437 — Critical (CVSS 9.8): All versions prior to 9.1.4 of Advantech WebAccess/SCADA are vulnerable to use of untrusted pointers. The RPC arguments…
CVE-2026-48137 — Critical (CVSS 9.1): There is an untrusted pointer dereference vulnerability in the NI grpc-device sideband streaming API that may allow an…
CVE-2025-4993 — Critical (CVSS 9.1): Untrusted Pointer Dereference vulnerability in RTI Connext Professional (Core Libraries) allows Pointer…
CVE-2025-1255 — Critical (CVSS 9.1): Untrusted Pointer Dereference vulnerability in RTI Connext Professional (Core Libraries) allows Pointer…
CVE-2024-36461 — Critical (CVSS 9.1): Within Zabbix, users have the ability to directly modify memory pointers in the JavaScript engine.

Browse all CWE-822 vulnerabilities →