cve.bz

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

8.2 highEPSS 0.6%

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

On this page
Certain size values in firmware binary headers could trigger out of bounds reads during signature validation, leading to denial of service or potentially limited leakage of information about out-of-bounds memory contents.

Severity

CVSS 3.1

8.2 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H
EPSS
0.6% (unchanged from 0.6% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 48th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2025-01-28. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-125 Out-of-bounds Read
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-26365 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2021-26365?via=ask-ai-copy and https://cve.bz/cve/CVE-2021-26365?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-26365 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_3_3200u_firmwarebefore picassopi-fp5_1.0.0.d
amd:ryzen_3_3250c_firmwarebefore picassopi-fp5_1.0.0.d
amd:ryzen_3_3250u_firmwarebefore picassopi-fp5_1.0.0.d
amd:amd_3015e_firmwarebefore pollockpi-ft5_1.0.0.3
amd:amd_3015ce_firmwarebefore pollockpi-ft5_1.0.0.3
amd:ryzen_7_5700u_firmwarebefore cezannepi-fp6_1.0.0.8
amd:ryzen_5_5500u_firmwarebefore cezannepi-fp6_1.0.0.8
amd:ryzen_3_5300u_firmwarebefore cezannepi-fp6_1.0.0.8
amd:ryzen_7_5700g_firmwarebefore cezannepi-fp6_1.0.0.8
amd:ryzen_7_5700ge_firmwarebefore cezannepi-fp6_1.0.0.8
amd:ryzen_5_5600g_firmwarebefore cezannepi-fp6_1.0.0.8
amd:ryzen_5_5600ge_firmwarebefore cezannepi-fp6_1.0.0.8
amd:ryzen_3_5300g_firmwarebefore cezannepi-fp6_1.0.0.8
amd:ryzen_3_5300ge_firmwarebefore cezannepi-fp6_1.0.0.8
amd:ryzen_9_6980hx_firmwarebefore rmb_1.0.0.4
amd:ryzen_9_6980hs_firmwarebefore rmb_1.0.0.4
amd:ryzen_9_6900hx_firmwarebefore rmb_1.0.0.4
amd:ryzen_9_6900hs_firmwarebefore rmb_1.0.0.4
amd:ryzen_7_6800h_firmwarebefore rmb_1.0.0.4
amd:ryzen_7_6800hs_firmwarebefore rmb_1.0.0.4
amd:ryzen_7_6800u_firmwarebefore rmb_1.0.0.4
amd:ryzen_5_6600h_firmwarebefore rmb_1.0.0.4
amd:ryzen_5_6600hs_firmwarebefore rmb_1.0.0.4
amd:ryzen_5_6600u_firmwarebefore rmb_1.0.0.4

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