cve.bz

CVE-2021-26384 amd: Out-of-bounds Read

7.8 highEPSS 0.2%

High (7.8) in amd. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
A malformed SMI (System Management Interface) command may allow an attacker to establish a corrupted SMI Trigger Info data structure, potentially leading to out-of-bounds memory reads and writes when triggering an SMI resulting in a potential loss of resources.

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 11th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWEs
CWE-125 Out-of-bounds Read
CWE-787 Out-of-bounds Write
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2021-26384 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2021-26384?via=ask-ai-copy and https://cve.bz/cve/CVE-2021-26384?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2021-26384 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
amd:ryzen_7_5700g_firmwarebefore comboam4_v2_pi_1.2.0.6c
amd:ryzen_7_5700ge_firmwarebefore comboam4_v2_pi_1.2.0.6c
amd:ryzen_5_5600g_firmwarebefore comboam4_v2_pi_1.2.0.6c
amd:ryzen_5_5600ge_firmwarebefore comboam4_v2_pi_1.2.0.6c
amd:ryzen_3_5300g_firmwarebefore comboam4_v2_pi_1.2.0.6c
amd:ryzen_3_5300ge_firmwarebefore comboam4_v2_pi_1.2.0.6c
amd:ryzen_9_5980hx_firmwarebefore cezannepi-fp6_1.0.0.9
amd:ryzen_9_5980hs_firmwarebefore cezannepi-fp6_1.0.0.9
amd:ryzen_7_5825u_firmwarebefore cezannepi-fp6_1.0.0.9
amd:ryzen_9_5900hx_firmwarebefore cezannepi-fp6_1.0.0.9
amd:ryzen_9_5900hs_firmwarebefore cezannepi-fp6_1.0.0.9
amd:ryzen_7_5825c_firmwarebefore cezannepi-fp6_1.0.0.9
amd:ryzen_7_5800h_firmwarebefore cezannepi-fp6_1.0.0.9
amd:ryzen_5_5625u_firmwarebefore cezannepi-fp6_1.0.0.9
amd:ryzen_7_5800hs_firmwarebefore cezannepi-fp6_1.0.0.9
amd:ryzen_5_5625c_firmwarebefore cezannepi-fp6_1.0.0.9
amd:ryzen_5_5600h_firmwarebefore cezannepi-fp6_1.0.0.9
amd:ryzen_5_5600hs_firmwarebefore cezannepi-fp6_1.0.0.9
amd:ryzen_7_5800u_firmwarebefore cezannepi-fp6_1.0.0.9
amd:ryzen_5_5600u_firmwarebefore cezannepi-fp6_1.0.0.9
amd:ryzen_5_5560u_firmwarebefore cezannepi-fp6_1.0.0.9
amd:ryzen_3_5425u_firmwarebefore cezannepi-fp6_1.0.0.9
amd:ryzen_3_5425c_firmwarebefore cezannepi-fp6_1.0.0.9
amd:ryzen_3_5400u_firmwarebefore cezannepi-fp6_1.0.0.9
amd:ryzen_3_5125c_firmwarebefore cezannepi-fp6_1.0.0.9
amd:ryzen_3_2200u_firmwarebefore comboam4v2_pi_1.2.0.6c
amd:ryzen_3_2300u_firmwarebefore comboam4v2_pi_1.2.0.6c
amd:ryzen_5_2500u_firmwarebefore comboam4v2_pi_1.2.0.6c
amd:ryzen_5_2600_firmwarebefore comboam4v2_pi_1.2.0.6c
amd:ryzen_5_2600h_firmwarebefore comboam4v2_pi_1.2.0.6c
amd:ryzen_5_2600x_firmwarebefore comboam4v2_pi_1.2.0.6c
amd:ryzen_5_2700_firmwarebefore comboam4v2_pi_1.2.0.6c
amd:ryzen_5_2700x_firmwarebefore comboam4v2_pi_1.2.0.6c
amd:ryzen_7_2700_firmwarebefore comboam4v2_pi_1.2.0.6c
amd:ryzen_7_2700u_firmwarebefore comboam4v2_pi_1.2.0.6c
amd:ryzen_7_2700x_firmwarebefore comboam4v2_pi_1.2.0.6c
amd:ryzen_7_2800h_firmwarebefore comboam4v2_pi_1.2.0.6c

Attack patterns (CAPEC)

  • CAPEC-540 Overread Buffers Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON