CVE-2021-46763
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 the SMU may enable a privileged attacker to write beyond the intended bounds of a shared memory buffer potentially leading to a loss of integrity.
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 input validation in the System Management Unit (SMU) allows a privileged attacker to perform out-of-bounds writes beyond the intended boundaries of a shared memory buffer, compromising data integrity.
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= milanpi_1.0.0.9= milanpi_1.0.0.9= milanpi_1.0.0.9= milanpi_1.0.0.9= milanpi_1.0.0.9= milanpi_1.0.0.9= milanpi_1.0.0.9= milanpi_1.0.0.9CVSS 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
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
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 modelRun 'dmidecode -t processor' or check /proc/cpuinfo to confirm the CPU model is one of the affected Epyc variants (72f3, 7313, 7313p, 7343, 7373x, 73f3, 7413, 7443)Affected if The processor is an AMD Epyc 72f3, 7313, 7313p, 7343, 7373x, 73f3, 7413, or 7443
-
Check the SMU firmware versionUse 'dmidecode -t bios' or access the BIOS/UEFI setup utility to view the System Management Unit firmware version. The version string typically appears as 'milanpi_x.x.x.x' or similarAffected if The reported SMU firmware version equals milanpi_1.0.0.9 exactly
-
Verify SMU interface accessibilityCheck if the SMU interface is accessible by examining /dev/cpu/*/msr or /sys/class/mic/mic0 (on systems with MCM packages) for read/write access by privileged usersAffected if Privileged users can directly read from or write to SMU memory regions without additional firmware-level validation
The system is affected if it uses an AMD Epyc processor from the affected list with SMU firmware version milanpi_1.0.0.9 installed.
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-supplied firmware updates for the System Management Unit. Review and restrict privileged access to SMU interfaces as a compensating control until patches are available.
- 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-2021-46763 — 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-46763 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