cve.bz

CVE-2021-26336 amd

5.5 mediumEPSS 0.2%

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

On this page
Insufficient bounds checking in System Management Unit (SMU) may cause invalid memory accesses/updates that could result in SMU hang and subsequent failure to service any further requests from other components.

Severity

CVSS 3.1

5.5 medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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; 12th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
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-26336 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2021-26336?via=ask-ai-copy and https://cve.bz/cve/CVE-2021-26336?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-26336 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:epyc_7003_firmwarebefore milanpi-sp3_1.0.0.4
amd:epyc_7002_firmwarebefore romepi-sp3_1.0.0.c
amd:epyc_72f3_firmwarebefore milanpi-sp3_1.0.0.4
amd:epyc_7313_firmwarebefore milanpi-sp3_1.0.0.4
amd:epyc_7313p_firmwarebefore milanpi-sp3_1.0.0.4
amd:epyc_7343_firmwarebefore milanpi-sp3_1.0.0.4
amd:epyc_73f3_firmwarebefore milanpi-sp3_1.0.0.4
amd:epyc_7413_firmwarebefore milanpi-sp3_1.0.0.4
amd:epyc_7443_firmwarebefore milanpi-sp3_1.0.0.4
amd:epyc_7443p_firmwarebefore milanpi-sp3_1.0.0.4
amd:epyc_7453_firmwarebefore milanpi-sp3_1.0.0.4
amd:epyc_74f3_firmwarebefore milanpi-sp3_1.0.0.4
amd:epyc_7513_firmwarebefore milanpi-sp3_1.0.0.4
amd:epyc_7543_firmwarebefore milanpi-sp3_1.0.0.4
amd:epyc_7543p_firmwarebefore milanpi-sp3_1.0.0.4
amd:epyc_75f3_firmwarebefore milanpi-sp3_1.0.0.4
amd:epyc_7643_firmwarebefore milanpi-sp3_1.0.0.4
amd:epyc_7663_firmwarebefore milanpi-sp3_1.0.0.4
amd:epyc_7713_firmwarebefore milanpi-sp3_1.0.0.4
amd:epyc_7713p_firmwarebefore milanpi-sp3_1.0.0.4
amd:epyc_7763_firmwarebefore milanpi-sp3_1.0.0.4
amd:epyc_7232p_firmwarebefore romepi-sp3_1.0.0.c
amd:epyc_7252_firmwarebefore romepi-sp3_1.0.0.c
amd:epyc_7262_firmwarebefore romepi-sp3_1.0.0.c
amd:epyc_7272_firmwarebefore romepi-sp3_1.0.0.c
amd:epyc_7282_firmwarebefore romepi-sp3_1.0.0.c
amd:epyc_7302_firmwarebefore romepi-sp3_1.0.0.c
amd:epyc_7302p_firmwarebefore romepi-sp3_1.0.0.c
amd:epyc_7352_firmwarebefore romepi-sp3_1.0.0.c
amd:epyc_7402_firmwarebefore romepi-sp3_1.0.0.c
amd:epyc_7402p_firmwarebefore romepi-sp3_1.0.0.c
amd:epyc_7452_firmwarebefore romepi-sp3_1.0.0.c
amd:epyc_7502_firmwarebefore romepi-sp3_1.0.0.c
amd:epyc_7502p_firmwarebefore romepi-sp3_1.0.0.c
amd:epyc_7532_firmwarebefore romepi-sp3_1.0.0.c
amd:epyc_7542_firmwarebefore romepi-sp3_1.0.0.c
amd:epyc_7552_firmwarebefore romepi-sp3_1.0.0.c
amd:epyc_7642_firmwarebefore romepi-sp3_1.0.0.c
amd:epyc_7662_firmwarebefore romepi-sp3_1.0.0.c
amd:epyc_7702_firmwarebefore romepi-sp3_1.0.0.c
amd:epyc_7702p_firmwarebefore romepi-sp3_1.0.0.c
amd:epyc_7742_firmwarebefore romepi-sp3_1.0.0.c
amd:epyc_7f32_firmwarebefore romepi-sp3_1.0.0.c
amd:epyc_7f52_firmwarebefore romepi-sp3_1.0.0.c

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-119 (12).

References

Check your stackJSON