AMD out-of-bounds write in TEE DrvSys

Check whether my systems are affected by CVE-2024-36344 (Insufficient parameter sanitization in AMD Secure Processor (ASP) TEE DrvSys could allow an attacker with local access to the Trusted…), 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-2024-36344 (entry last updated 2026-11-13):
Affected:
- AMD AMD EPYC™ 4004 Series Processors: version range not reported
- AMD AMD EPYC™ 9005 Series Processors: version range not reported
- 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™ 3000 Series Desktop Processors: version range not reported
- and 40 more affected products, listed on https://cve.now/CVE-2024-36344
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2024-36344 is not listed as of cve.now's last read.
This KEV status is for CVE-2024-36344 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-4018.html
- https://www.amd.com/en/resources/product-security/bulletin/AMD-SB-6028.html
- https://www.amd.com/en/resources/product-security/bulletin/AMD-SB-3057.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-2024-36344
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-2024-36344"}.