AMD Secure Processor TEE DrvSys: weak parameter checks allow out-of-bounds write

CVSS 6.9CVE-2024-36344Firmware, BMC & network fabriccurated

Impact

The DrvSys component of the AMD Secure Processor's Trusted Execution Environment does not sanitize its parameters properly, which allows an out-of-bounds write. AMD says this could cause loss of platform integrity or denial of service. The Secure Processor is the root of trust under SEV-SNP tenant isolation, so a platform integrity issue on EPYC 9005 and EPYC 4004 hosts matters on any shared node. The record does not say whether confidential-VM guarantees are directly affected.

Who can reach it

An attacker with local access to the TEE interface or to a Trusted Application. That means privileged code on the host, not an ordinary tenant workload. The record scores it as local with low privileges.

What to do

Apply the AMD platform firmware update that fixes this, delivered as a BIOS/AGESA release from the server OEM, per AMD-SB-3057, AMD-SB-4018 and AMD-SB-6028. The record does not give fixed firmware versions; check the bulletins. Flashing takes each node out of service and needs a reboot, so drain GPU workloads first.

References

https://nvd.nist.gov/vuln/detail/CVE-2024-36344 https://www.amd.com/en/resources/product-security/bulletin/AMD-SB-3057.html 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

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.