CVE-2024-36344 · Infrastructure
NO FIX YET
AMD Secure Processor's TEE DrvSys does not sanitize some parameters, so code with local access to the TEE interface or a Trusted Application can trigger an out-of-bounds write. The result can be loss of platform integrity or a denial of service.
first public Nov 12, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Affects AMD systems with the Secure Processor TEE. The attacker must already have local access to the TEE interface or a Trusted Application, so exposure from the network is not described. The sources do not name affected firmware or product versions.
Not affected if no-local-access
Who cares amd, firmware, secure-processor, tee
Unknown from the sources.
No fix yet, per the sources.
Insufficient parameter sanitization in AMD Secure Processor (ASP) TEE DrvSys could allow an attacker with local access to the Trusted Execution Environment (TEE) interface or Trusted Application (TA) to cause an out-of-bounds write, potentially resulting in a loss of platform integrity or denial of service.
This page as .md · .json · CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.