CVE-2021-46748
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 bounds checking in the ASP (AMD Secure Processor) may allow an attacker to access memory outside the bounds of what is permissible to a TA (Trusted Application) resulting in a potential denial of service.
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 bounds checking in the AMD Secure Processor (ASP) allows a Trusted Application (TA) to access memory outside its allocated bounds, potentially causing a denial of service. This is a firmware-level vulnerability in AMD's dedicated security processor that manages trusted execution environments.
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< 23.10.01.46< 23.7.1< 23.q3all versionsall versionsall versionsall versionsCVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 AMD Secure Processor firmware versionUse 'msinfo32' or the AMD Ryzen Master software to locate the AMD Secure Processor firmware version, or check the UEFI/BIOS for Secure Processor informationAffected if The firmware version is below 23.10.01.46 for Intel Radeon Rx Vega M, or the product is one of the AMD Radeon Rx Vega 56/64 or Pro Vega 56/64 variants (all versions affected)
-
Determine installed GPU modelOpen Device Manager, run 'lspci -v' on Linux, or use GPU-Z to identify the exact AMD graphics card model (Vega M, Rx Vega 56, Rx Vega 64, Pro Vega 56, or Pro Vega 64)Affected if The system contains an Intel Radeon Rx Vega M, AMD Rx Vega 56, AMD Rx Vega 64, AMD Pro Vega 56, or AMD Pro Vega 64 graphics adapter
-
Check AMD Radeon Software versionOpen AMD Radeon Software (Radeon Settings), click the gear icon, and view the software version under 'About' or check 'Programs and Features' in WindowsAffected if The AMD Radeon Software version is below 23.7.1 or below 23.q3 for the listed consumer versions
-
Verify Trusted Application execution statusCheck if any Trusted Applications are actively running or have been executed on the system. This may require reviewing security logs or using AMD-specific diagnostic tools if availableAffected if Trusted Applications are enabled or have been executed on the system using the AMD Secure Processor
A system is affected if it contains an AMD or Intel Vega M graphics product AND runs firmware/software versions below the patched releases, with Trusted Applications enabled on the AMD Secure Processor.
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 data23.q323.7.123.10.01.46
Apply the AMD-provided firmware/security update for the AMD Secure Processor. Verify that TA memory isolation is enforced correctly after the update.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-46748 — 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-46748 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