cve.bz

CVE-2026-0470 amd: NULL Pointer Dereference

6.8 mediumEPSS 0.1%

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

On this page
Null pointer dereference in AMD Embedded SPI Flash driver could allow a local user to potentially cause a loss of availability.

Severity

CVSS 4.0

6.8 medium
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
EPSS
0.1% estimated probability of exploitation activity in the next 30 days; 2nd percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-12. 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-476 NULL Pointer Dereference
OWASP Top 10
A10:2025 Mishandling of Exceptional Conditions
Published
Modified
Assigned by
AMD (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

ChatGPTClaudeGoogle AI Mode

Show the promptExplain CVE-2026-0470 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-0470?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-0470?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-2026-0470 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.

Badge for a README or a site

CVE-2026-0470

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-0470](https://cve.bz/cve/badge/CVE-2026-0470.svg)](https://cve.bz/cve/CVE-2026-0470)

HTML:

<a href="https://cve.bz/cve/CVE-2026-0470"><img src="https://cve.bz/cve/badge/CVE-2026-0470.svg" alt="CVE-2026-0470"></a>

Affected

  • amd:amd epyc™ embedded 3000 series processors
  • amd:amd ryzen™ embedded r1000 series processors
  • amd:amd ryzen™ embedded r2000 series processors
  • amd:amd ryzen™ embedded v1000 series processors (formerly codenamed "raven ridge")
  • amd:amd ryzen™ embedded v2000 series processors

References

Check your stackJSON