CVE-2023-20548
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 · uneditedA Time-of-check time-of-use (TOCTOU) race condition in the AMD Secure Processor (ASP) could allow an attacker to corrupt memory resulting in loss of integrity, confidentiality, or availability.
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 confidenceA Time-of-check time-of-use (TOCTOU) race condition in the AMD Secure Processor (ASP) allows an attacker to corrupt memory. The vulnerability exists in the secure firmware/hardware layer of AMD processors, potentially allowing privilege escalation or memory manipulation at the firmware level.
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< 6.2.0< 25.q2< 24.6.1all 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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/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.
-
Check installed ROCm versionRun 'rocminfo' or check installed package version using system package manager (dpkg/rpm) for rocm packagesAffected if ROCm version is installed and less than 6.2.0
-
Check AMD Radeon Software versionCheck installed Radeon Software version via system installed programs list, or check the installation directory for version infoAffected if Radeon Software version is less than 24.6.1 or less than 25.q2 (development branch)
-
Identify GPU modelUse system GPU info tools (lspci, GPU-Z on Windows, or manufacturer diagnostic tools) to identify the installed AMD graphics card modelAffected if The GPU is a Radeon VII or Radeon Pro VII (any firmware version)
-
Check AMD Secure Processor firmware versionAccess BIOS/UEFI settings or use AMD diagnostic tools to query the Secure Processor firmware version if availableAffected if Secure Processor firmware is present and has not been patched to the corrected version (contact AMD for specific firmware versions)
A system is affected if it has ROCm < 6.2.0, Radeon Software < 24.6.1/25.q2, or uses a Radeon VII / Radeon Pro VII graphics card with any firmware version.
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 data6.2.024.6.125.q2
Apply AMD-provided firmware updates for the Secure Processor; verify with AMD's security advisory for specific processor models and follow platform-specific update procedures.
- Consultation8.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 $9,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-20548 — 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-2023-20548 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