CVE
Use of uninitialized or invalid state in AMD Graphics Driver could allow a local attacker to write out of bounds, potentially resulting in…
A 0-10 score for how bad the bug is in the worst case. It does not say how common the affected setup is.What do these mean? →6.9MediumCNA
- Exploited
- No known exploitation
- Fix
- See vendor advisory
- Who is exposed
- Not reported
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 29/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
An uninitialized or invalid state flaw in the AMD Graphics Driver, as shipped on certain AMD Ryzen Embedded processors, lets an attacker write out of bounds, potentially causing loss of integrity or denial of service. The attacker can reach it remotely over the network, without logging in and without any user action.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
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.
cve.now Index
29Pcve.now Index 29 of 100 · methodology v3 · provisional
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.9/10CVSS 6.9
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 74 if added to CISA KEV
- Would score about 69 if CISA's SSVC rates exploitation active
- Would score about 34 if advisories confirm default setups are exposed
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-48479 (Use of uninitialized or invalid state in AMD Graphics Driver could allow a local attacker to write out of bounds, potentially resulting in…), 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-48479 (entry last updated 2026-11-11):
Affected:
- 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
- AMD AMD Ryzen™ Embedded V1000 Series Processors (formerly codenamed "Picasso"): 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-48479 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-48479 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-4026.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-48479
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-48479"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- 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
- AMD AMD Ryzen™ Embedded V1000 Series Processors (formerly codenamed "Picasso")
Version range not reported
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Link
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.