CVE-2021-46757 is a high severity flaw in the AMD Secure Processor (ASP) Secure OS on some Ryzen Embedded parts, scored 7.8 by NVD. Insufficient buffer checking could let a malicious trusted application reach kernel memory. AMD ships the fix as Platform Initialization firmware, so apply the version in bulletin AMD-SB-5001.
What's affected
The record describes insufficient checking of a memory buffer in ASP Secure OS, which may allow an attacker with a malicious trusted application to read and write the ASP Secure OS kernel virtual address space, potentially leading to privilege escalation. The record lists the Ryzen Embedded 5900E and 5950E among others. The vector is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H: a local attacker with low privileges.
AMD's bulletin AMD-SB-5001, published 2024-02-13 as AMD Embedded Processors Vulnerabilities, rates this CVE High, which matches NVD. Mitigations are delivered through Platform Initialization (PI) firmware packages. For the Ryzen Embedded 5000 series the bulletin lists EmbAM4PI 1.0.0.0, dated 2022-04-29, as the minimum version. The bulletin also lists the R1000 and R2000 series as not affected. One Ryzen Embedded V series column lists EmbeddedPI-FP6 1.0.0.6 as the minimum, and I could not map that column to a specific model with confidence, so read the table for your exact part number.
The CVE was assigned long before the bulletin appeared, and NVD published its record in February 2024. The record and the bulletin agree on severity.
Weakness class: CWE-119.
How to check if you're exposed
Find out which processor families you run, from the part number on the board or your asset records. Then find the PI firmware version in the system firmware, which your board or system vendor exposes in its firmware setup screen or its update tool.
Compare that version with the minimum in AMD's table for your family. For Ryzen Embedded 5000 that is EmbAM4PI 1.0.0.0 or later. You usually receive PI firmware through your board or system vendor's BIOS update, not directly from AMD, so ask them which release includes the PI version you need.
If the system firmware is older than April 2022, assume it is in scope until the vendor says otherwise.
What to do now
- Build a list of embedded systems that use Ryzen Embedded 5000 or V series parts.
- Read the AMD-SB-5001 table and note the minimum PI version for each family.
- Ask each board or system vendor for the firmware release that includes that PI version.
- Schedule the update, and stage it on one unit first since this is low level firmware.
- Restrict who can install or run trusted applications on the devices until the update is done.
Why it matters
The ASP is a separate security processor on the chip. It runs its own small operating system and hosts trusted applications. The record describes a buffer check that was too weak, so a trusted application that is malicious could reach memory it should not. The record files it under CWE-119, improper restriction of operations within the bounds of a memory buffer.
Because the attacker has to run a trusted application already, this is a privilege escalation inside a platform that is meant to be isolated, not an entry point. Its value to an attacker is the position it gives: code running in the security processor sits below the normal operating system.
Firmware flaws are slow to close, since the fix travels through chip vendor, board maker and finally the operator. An inventory that records firmware versions, not just operating systems, shortens that path.
This CVE is not listed in the CISA Known Exploited Vulnerabilities catalog, and none of the pages I read state that it is exploited in the wild. That is a statement about what is known, not a reason to delay the fix.
Quick check
Which firmware fixes CVE-2021-46757?
AMD's bulletin AMD-SB-5001 lists PI firmware versions per family. For Ryzen Embedded 5000 it lists EmbAM4PI 1.0.0.0. Check the table for your family.
Can someone exploit it from the network?
The record vector is local with low privileges, and the description requires a malicious trusted application.
Sources
Last reviewed: 19 October 2026.