CVE-2021-46757
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedInsufficient checking of memory buffer in ASP Secure OS may allow an attacker with a malicious TA to read/write to the ASP Secure OS kernel virtual address space potentially leading to privilege escalation.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceInsufficient memory buffer checking in ASP Secure OS allows a malicious Trusted Application (TA) to read/write to the kernel virtual address space, enabling privilege escalation from the TA execution context to the secure kernel.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< embam4pi_1.0.0.0< embam4pi_1.0.0.0< embam4pi_1.0.0.0< embam4pi_1.0.0.0< embeddedpi-fp6_1.0.0.6< embeddedpi-fp6_1.0.0.6< embeddedpi-fp6_1.0.0.6< embeddedpi-fp6_1.0.0.6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the AMD Ryzen Embedded processor modelCheck the system information or use commands like 'dmidecode -t processor' or check the processor label on the hardware to confirm the exact model (e.g., 5950e, 5900e, 5800e, 5600e, V2516, V2546, V2718, V2748)Affected if The processor is one of the models listed in the affected products
-
Check the firmware versionUse platform-specific tools (such as AMD's firmware update utilities, BIOS/UEFI setup, or system management interfaces) to retrieve the current ASP Secure OS firmware version. For 5950e/5900e/5800/5600e, look for version 'embam4pi'. For V2516/V2546/V2718/V2748, look for version 'embeddedpi-fp6'. Compare the installed version against embam4pi_1.0.0.0 or embeddedpi-fp6_1.0.0.6 respectivelyAffected if The firmware version is lower than embam4pi_1.0.0.0 (for 5950e/5900e/5800e/5600e) or lower than embeddedpi-fp6_1.0.0.6 (for V2516/V2546/V2718/V2748)
-
Verify if Trusted Applications are running in the secure environmentCheck the system configuration to determine if Trusted Applications (TAs) are being loaded and executed in the AMD Secure Processor (ASP) secure OS environment. Review any security policies or TA loading configurationsAffected if Trusted Applications are loaded and executing in the secure OS context
A system is affected if it uses one of the vulnerable AMD Ryzen Embedded processor models with firmware versions below the fixed releases AND has Trusted Applications running in the ASP Secure OS environment.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor-provided security updates for the affected Secure OS implementation; ensure only trusted and validated TAs are permitted to execute in the secure environment.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-46757 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-46757 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data