CVE-2026-48479: AMD Graphics Driver uninitialized state out-of-bounds write

CVE-2026-48479 · Severity: info · Published 2026-11-11

AMD's graphics driver contains a flaw where uninitialized memory state can lead to out-of-bounds writes, allowing a local attacker to corrupt data or crash the system. This could undermine system stability or data integrity on machines with AMD graphics hardware.

Vendors: Amd.

Quick answers

Is CVE-2026-48479 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-48479 being exploited in the wild.
How severe is CVE-2026-48479?
Informational severity, published 11 November 2026.
Which products and versions are affected?
AMD Graphics Driver.
Is there a fix for CVE-2026-48479?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-48479 attacked?
It is attacked with local access.
Am I affected by CVE-2026-48479?
Check whether you run Amd Graphics Driver. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

Use of uninitialized or invalid state in the AMD Graphics Driver permits out-of-bounds memory writes by a local attacker. The vulnerability is reachable from the local system only and may result in loss of data integrity or denial of service. No public exploit code is known at this time.

Affected products

  • AMD Graphics Driver

Timeline

  • 2026-11-11: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.