CVE-2021-46769
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 syscall input validation in the ASP Bootloader may allow a privileged attacker to execute arbitrary DMA copies, which can lead to code execution.
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 syscall input validation in the ASP Bootloader allows a privileged attacker to manipulate DMA copy operations through unsanitized syscall parameters, potentially achieving arbitrary code execution.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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.
-
Identify the installed AMD Epyc processor modelCheck the server's CPU model using system information tools (e.g., dmidecode, lshw, or cat /proc/cpuinfo) to determine if it matches one of the affected processors: Epyc 72f3, 7313, 7313p, 7343, 7373x, 73f3, 7413, or 7443Affected if The processor is an AMD Epyc model from the affected list (72f3, 7313, 7313p, 7343, 7373x, 73f3, 7413, 7443)
-
Check the firmware version stringRetrieve the BMC or system firmware version. On AMD Epyc servers, this is typically available via BMC interfaces (IPMI, Redfish) or by checking the BIOS/UEFI version reported by the system. Look for the string 'milanpi_1.0.0.9'Affected if The firmware version is exactly milanpi_1.0.0.9 for the listed processor models
-
Verify the ASP Bootloader component is presentInspect the firmware image or bootloader configuration if accessible through BMC firmware extraction tools or vendor-provided firmware analysis utilities. Check for the presence of the 'ASP Bootloader' component in the firmware versionAffected if The ASP Bootloader component exists in the firmware build for the affected version
-
Confirm DMA syscall interface is exposedIf the system provides debug or diagnostic interfaces (such as BMC shell, vendor firmware update tools, or crash dump analysis), examine whether DMA copy syscall interfaces from the bootloader are exposed or callable. This typically requires firmware-level debugging capabilitiesAffected if DMA-related syscall interfaces from the bootloader are accessible or enabled in the environment
The environment is affected if it runs an AMD Epyc processor from the listed models with firmware version milanpi_1.0.0.9 and the ASP Bootloader with its DMA syscall interface is present.
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 dataImplement rigorous input validation and bounds checking on all syscall parameters related to DMA operations in the bootloader; deploy updated firmware with proper sanitization.
- Consultation2.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 $4,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-46769 — 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-46769 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