cve.bz

CVE-2026-48479 amd: Out-of-bounds Write

6.9 mediumEPSS 0.3%

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

On this page
Use of uninitialized or invalid state in AMD Graphics Driver could allow a local attacker to write out of bounds, potentially resulting in loss of integrity or denial of service.

Severity

CVSS 4.0

6.9 medium
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
EPSS
0.3% estimated probability of exploitation activity in the next 30 days; 25th 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-787 Out-of-bounds Write
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-48479 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-48479?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-48479?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-48479 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-48479

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-48479](https://cve.bz/cve/badge/CVE-2026-48479.svg)](https://cve.bz/cve/CVE-2026-48479)

HTML:

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

Affected

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

References

Check your stackJSON