CVE-2023-20533
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 DRAM address validation in System Management Unit (SMU) may allow an attacker to read/write from/to an invalid DRAM address, potentially resulting in 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 · high confidenceInsufficient DRAM address validation in AMD's System Management Unit (SMU) allows an attacker to read from or write to invalid DRAM addresses. This could enable denial-of-service through memory corruption or system instability.
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< romepi_1.0.0.d< romepi_1.0.0.d< romepi_1.0.0.d< romepi_1.0.0.d< romepi_1.0.0.d< romepi_1.0.0.d< romepi_1.0.0.d< romepi_1.0.0.dCVSS 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 Epyc processor modelUse system information commands such as `lscpu`, `dmidecode -t processor`, or check the BIOS/UEFI setup to identify the exact AMD Epyc processor model numberAffected if The processor model is one of: Epyc 7232p, 7252, 7262, 7272, 7282, 7302, 7302p, or 7352
-
Determine the SMU firmware versionAccess the BMC/IPMI interface or use vendor-specific tools to retrieve the System Management Unit firmware version. On some systems, this may be visible in BIOS update utilities or through `ipmi` commands such as `ipmi-fru` or `ipmi-sel`Affected if The firmware version cannot be confirmed as romepi_1.0.0.d or later
-
Compare installed firmware against affected versionLocate the SMU or BIOS firmware version information in the system management interface, BIOS setup, or firmware update logs, then compare it to the version threshold romepi_1.0.0.dAffected if The installed firmware version is less than romepi_1.0.0.d (for example, romepi_1.0.0.c or earlier)
-
Check if SMU address validation is exploitableReview system logs for any memory corruption errors, unexpected system instability, or anomalous DRAM access patterns that may indicate exploitation of invalid DRAM address handlingAffected if The system exhibits unexplained memory corruption or instability consistent with invalid DRAM address access, and the firmware version is below the patched level
A user is affected if they are running any of the listed AMD Epyc processor models with SMU firmware versions earlier than romepi_1.0.0.d.
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/microcode updates for affected processors. Contact AMD or system OEMs for specific patch availability and deployment guidance.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-20533 — 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-20533 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