CVE-2021-26367

A malicious attacker in x86 can misconfigure the Trusted Memory Regions (TMRs), which may allow the attacker to set an arbitrary address range for the TMR, potentially leading to a loss of integrity and availability.

Published: 2024-08-13 Last update: 2024-12-12 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2021-26367 is rated Low Risk (26.1/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.04%). 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-26367

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 2024-08-14 — 0.04% —

Full EPSS history (1 record total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.7 3.1 MEDIUM
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/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:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
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:N)
Doesn’t really leak secrets in a meaningful 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.
 0.5 5.2 [email protected]
6.0 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/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:H)
They need powerful rights—admin, root, or similar—before this pays off.
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:N)
Doesn’t really leak secrets in a meaningful 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.
 0.8 5.2 [email protected]

Weakness enumeration for CVE-2021-26367

Affected software / configurations for CVE-2021-26367

Vendor Product Version Raw CPE
amd radeon_software < 23.12.1 cpe:2.3:a:amd:radeon_software:*:*:*:*:adrenalin:*:*:*
amd radeon_software <= 23.q4 cpe:2.3:a:amd:radeon_software:*:*:*:*:pro:*:*:*
amd ryzen_9_5980hx_firmware < cezannepi-fp6_1.0.0.6 cpe:2.3:o:amd:ryzen_9_5980hx_firmware:*:*:*:*:*:*:*:*
amd ryzen_3_3300u_firmware < picassopi-fp5_1.0.0.e cpe:2.3:o:amd:ryzen_3_3300u_firmware:*:*:*:*:*:*:*:*
amd ryzen_3_3350u_firmware < picassopi-fp5_1.0.0.e cpe:2.3:o:amd:ryzen_3_3350u_firmware:*:*:*:*:*:*:*:*
amd ryzen_5_3450u_firmware < picassopi-fp5_1.0.0.e cpe:2.3:o:amd:ryzen_5_3450u_firmware:*:*:*:*:*:*:*:*
amd ryzen_5_3500u_firmware < picassopi-fp5_1.0.0.e cpe:2.3:o:amd:ryzen_5_3500u_firmware:*:*:*:*:*:*:*:*
amd ryzen_5_3500c_firmware < picassopi-fp5_1.0.0.e cpe:2.3:o:amd:ryzen_5_3500c_firmware:*:*:*:*:*:*:*:*
amd ryzen_5_3550h_firmware < picassopi-fp5_1.0.0.e cpe:2.3:o:amd:ryzen_5_3550h_firmware:*:*:*:*:*:*:*:*
amd ryzen_5_3580u_firmware < picassopi-fp5_1.0.0.e cpe:2.3:o:amd:ryzen_5_3580u_firmware:*:*:*:*:*:*:*:*
amd ryzen_7_3700u_firmware < picassopi-fp5_1.0.0.e cpe:2.3:o:amd:ryzen_7_3700u_firmware:*:*:*:*:*:*:*:*
amd ryzen_7_3700c_firmware < picassopi-fp5_1.0.0.e cpe:2.3:o:amd:ryzen_7_3700c_firmware:*:*:*:*:*:*:*:*
amd ryzen_7_3750h_firmware < picassopi-fp5_1.0.0.e cpe:2.3:o:amd:ryzen_7_3750h_firmware:*:*:*:*:*:*:*:*
amd ryzen_7_3780u_firmware < picassopi-fp5_1.0.0.e cpe:2.3:o:amd:ryzen_7_3780u_firmware:*:*:*:*:*:*:*:*
amd athlon_gold_3150c_firmware < picassopi-fp5_1.0.0.e cpe:2.3:o:amd:athlon_gold_3150c_firmware:*:*:*:*:*:*:*:*
amd athlon_gold_3150u_firmware < picassopi-fp5_1.0.0.e cpe:2.3:o:amd:athlon_gold_3150u_firmware:*:*:*:*:*:*:*:*
amd athlon_pro_3145b_firmware < picassopi-fp5_1.0.0.e cpe:2.3:o:amd:athlon_pro_3145b_firmware:*:*:*:*:*:*:*:*
amd athlon_silver_3050c_firmware < picassopi-fp5_1.0.0.e cpe:2.3:o:amd:athlon_silver_3050c_firmware:*:*:*:*:*:*:*:*
amd athlon_silver_3050u_firmware < picassopi-fp5_1.0.0.e cpe:2.3:o:amd:athlon_silver_3050u_firmware:*:*:*:*:*:*:*:*
amd athlon_pro_3045b_firmware < picassopi-fp5_1.0.0.e cpe:2.3:o:amd:athlon_pro_3045b_firmware:*:*:*:*:*:*:*:*
amd athlon_silver_3050e_firmware < picassopi-fp5_1.0.0.e cpe:2.3:o:amd:athlon_silver_3050e_firmware:*:*:*:*:*:*:*:*
amd athlon_gold_pro_3150g_firmware < comboam4pi_1.0.0.9 cpe:2.3:o:amd:athlon_gold_pro_3150g_firmware:*:*:*:*:*:*:*:*
amd athlon_gold_3150g_firmware < comboam4pi_1.0.0.9 cpe:2.3:o:amd:athlon_gold_3150g_firmware:*:*:*:*:*:*:*:*
amd athlon_gold_pro_3150ge_firmware < comboam4pi_1.0.0.9 cpe:2.3:o:amd:athlon_gold_pro_3150ge_firmware:*:*:*:*:*:*:*:*
amd athlon_pro_300ge_firmware < comboam4pi_1.0.0.9 cpe:2.3:o:amd:athlon_pro_300ge_firmware:*:*:*:*:*:*:*:*
amd ryzen_3_4300ge_firmware < comboam4v2_pi_1.2.0.5 cpe:2.3:o:amd:ryzen_3_4300ge_firmware:*:*:*:*:*:*:*:*
amd ryzen_5_4600ge_firmware < comboam4v2_pi_1.2.0.5 cpe:2.3:o:amd:ryzen_5_4600ge_firmware:*:*:*:*:*:*:*:*
amd ryzen_7_4700ge_firmware < comboam4v2_pi_1.2.0.5 cpe:2.3:o:amd:ryzen_7_4700ge_firmware:*:*:*:*:*:*:*:*
amd ryzen_3_4300g_firmware < comboam4v2_pi_1.2.0.5 cpe:2.3:o:amd:ryzen_3_4300g_firmware:*:*:*:*:*:*:*:*
amd ryzen_5_4600g_firmware < comboam4v2_pi_1.2.0.5 cpe:2.3:o:amd:ryzen_5_4600g_firmware:*:*:*:*:*:*:*:*
amd ryzen_7_4700g_firmware < comboam4v2_pi_1.2.0.5 cpe:2.3:o:amd:ryzen_7_4700g_firmware:*:*:*:*:*:*:*:*
amd ryzen_3_5300ge_firmware < comboam4v2_pi_1.2.0.5 cpe:2.3:o:amd:ryzen_3_5300ge_firmware:*:*:*:*:*:*:*:*
amd ryzen_3_5300g_firmware < comboam4v2_pi_1.2.0.5 cpe:2.3:o:amd:ryzen_3_5300g_firmware:*:*:*:*:*:*:*:*
amd ryzen_5_5600ge_firmware < comboam4v2_pi_1.2.0.5 cpe:2.3:o:amd:ryzen_5_5600ge_firmware:*:*:*:*:*:*:*:*
amd ryzen_5_5600g_firmware < comboam4v2_pi_1.2.0.5 cpe:2.3:o:amd:ryzen_5_5600g_firmware:*:*:*:*:*:*:*:*
amd ryzen_7_5700ge_firmware < comboam4v2_pi_1.2.0.5 cpe:2.3:o:amd:ryzen_7_5700ge_firmware:*:*:*:*:*:*:*:*
amd ryzen_7_5700g_firmware < comboam4v2_pi_1.2.0.5 cpe:2.3:o:amd:ryzen_7_5700g_firmware:*:*:*:*:*:*:*:*

References for CVE-2021-26367

cvelogic Threat Intelligence