CVE-2021-26391

Insufficient verification of multiple header signatures while loading a Trusted Application (TA) may allow an attacker with privileges to gain code execution in that TA or the OS/kernel.

Published: 2022-11-09 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2021-26391 is rated Low Risk (33.7/100): CVSS High severity, with low exploitation likelihood (EPSS 0.17%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2021-26391

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.06% 0.17% +0.11%
2 2026-05-10 0.03% 0.06% +0.03%
3 2025-05-02 — 0.03% —

Full EPSS history (7 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2021-26391

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.8 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 5.9 [email protected]
7.8 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2021-26391

OS Trackers for CVE-2021-26391

vendor priority summary link
redhat medium — https://access.redhat.com/security/cve/CVE-2021-26391

Affected software / configurations for CVE-2021-26391

Vendor Product Version Raw CPE
amd enterprise_driver < 22.10.20 cpe:2.3:a:amd:enterprise_driver:*:*:*:*:*:*:*:*
amd radeon_pro_software < 22.q2 cpe:2.3:a:amd:radeon_pro_software:*:*:*:*:enterprise:*:*:*
amd radeon_software < 22.5.2 cpe:2.3:a:amd:radeon_software:*:*:*:*:*:*:*:*
amd radeon_rx_vega_56_firmware — cpe:2.3:o:amd:radeon_rx_vega_56_firmware:-:*:*:*:*:*:*:*
amd radeon_rx_vega_64_firmware — cpe:2.3:o:amd:radeon_rx_vega_64_firmware:-:*:*:*:*:*:*:*
amd ryzen_3_5300ge_firmware — cpe:2.3:o:amd:ryzen_3_5300ge_firmware:-:*:*:*:*:*:*:*
amd ryzen_3_5300g_firmware — cpe:2.3:o:amd:ryzen_3_5300g_firmware:-:*:*:*:*:*:*:*
amd ryzen_5_5600ge_firmware — cpe:2.3:o:amd:ryzen_5_5600ge_firmware:-:*:*:*:*:*:*:*
amd ryzen_5_5600g_firmware — cpe:2.3:o:amd:ryzen_5_5600g_firmware:-:*:*:*:*:*:*:*
amd ryzen_7_5700ge_firmware — cpe:2.3:o:amd:ryzen_7_5700ge_firmware:-:*:*:*:*:*:*:*
amd ryzen_7_5700g_firmware — cpe:2.3:o:amd:ryzen_7_5700g_firmware:-:*:*:*:*:*:*:*
amd ryzen_3_5300u_firmware — cpe:2.3:o:amd:ryzen_3_5300u_firmware:-:*:*:*:*:*:*:*
amd ryzen_5_5500u_firmware — cpe:2.3:o:amd:ryzen_5_5500u_firmware:-:*:*:*:*:*:*:*
amd ryzen_7_5700u_firmware — cpe:2.3:o:amd:ryzen_7_5700u_firmware:-:*:*:*:*:*:*:*
amd ryzen_3_5400u_firmware — cpe:2.3:o:amd:ryzen_3_5400u_firmware:-:*:*:*:*:*:*:*
amd ryzen_5_5560u_firmware — cpe:2.3:o:amd:ryzen_5_5560u_firmware:-:*:*:*:*:*:*:*
amd ryzen_5_5600u_firmware — cpe:2.3:o:amd:ryzen_5_5600u_firmware:-:*:*:*:*:*:*:*
amd ryzen_5_5600h_firmware — cpe:2.3:o:amd:ryzen_5_5600h_firmware:-:*:*:*:*:*:*:*
amd ryzen_5_5600hs_firmware — cpe:2.3:o:amd:ryzen_5_5600hs_firmware:-:*:*:*:*:*:*:*
amd ryzen_7_5800u_firmware — cpe:2.3:o:amd:ryzen_7_5800u_firmware:-:*:*:*:*:*:*:*
amd ryzen_7_5800h_firmware — cpe:2.3:o:amd:ryzen_7_5800h_firmware:-:*:*:*:*:*:*:*
amd ryzen_7_5800hs_firmware — cpe:2.3:o:amd:ryzen_7_5800hs_firmware:-:*:*:*:*:*:*:*
amd ryzen_9_5900hs_firmware — cpe:2.3:o:amd:ryzen_9_5900hs_firmware:-:*:*:*:*:*:*:*
amd ryzen_9_5900hx_firmware — cpe:2.3:o:amd:ryzen_9_5900hx_firmware:-:*:*:*:*:*:*:*
amd ryzen_9_5980hs_firmware — cpe:2.3:o:amd:ryzen_9_5980hs_firmware:-:*:*:*:*:*:*:*
amd ryzen_9_5980hx_firmware — cpe:2.3:o:amd:ryzen_9_5980hx_firmware:-:*:*:*:*:*:*:*

References for CVE-2021-26391

cvelogic Threat Intelligence