CVE-2021-46765
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 input validation in ASP may allow an attacker with a compromised SMM to induce out-of-bounds memory reads within the ASP, potentially leading to a 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 confidenceThis vulnerability exists in the AMD Secure Processor (ASP) firmware where insufficient input validation allows an attacker who has already compromised System Management Mode (SMM) to trigger out-of-bounds memory reads within the ASP. The flaw enables a local attacker with privileged SMM access to potentially cause denial of service through memory corruption in the security processor.
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= rembrandtpi-fp7_1.0.0.5= rembrandtpi-fp7_1.0.0.5= rembrandtpi-fp7_1.0.0.5= rembrandtpi-fp7_1.0.0.5= rembrandtpi-fp7_1.0.0.5= rembrandtpi-fp7_1.0.0.5= rembrandtpi-fp7_1.0.0.5= rembrandtpi-fp7_1.0.0.5CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 the AMD Ryzen processor modelCheck system information to confirm the processor is one of the affected models: Ryzen 6600h, 6600hs, 6600u, 6800h, 6800hs, 6800u, 6900hs, or 6900hxAffected if The system uses any of these eight Ryzen mobile processor models
-
Determine the AMD Secure Processor firmware versionAccess the AMD Secure Processor (ASP) firmware version through BIOS settings, AMD utilities, or system firmware information tools. Look for a firmware identifier starting with 'rembrandtpi-fp7'Affected if The ASP firmware version is exactly rembrandtpi-fp7_1.0.0.5
-
Verify the exact firmware version stringConfirm the complete firmware version string matches 'rembrandtpi-fp7_1.0.0.5' exactly. No partial matches or other versions are affected by this specific CVEAffected if The installed firmware version string equals rembrandtpi-fp7_1.0.0.5
-
Assess SMM integrity as a prerequisiteReview whether the System Management Mode has been compromised, since this vulnerability requires an attacker with existing privileged SMM accessAffected if SMM integrity cannot be verified or shows signs of compromise, making the ASP vulnerability exploitable
A system is affected only if it uses one of the eight listed Ryzen processors with exactly the firmware version rembrandtpi-fp7_1.0.0.5 and the attacker already has SMM privilege.
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 AMD-provided firmware updates for the Secure Processor when available. Since exploitation requires pre-compromised SMM, ensure SMM integrity through secure boot mechanisms and BIOS updates.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.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 $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-46765 — 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-46765 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