Skip to content
Noroxi
NVD / CVE Program· CNA AMD

CVE-2021-46774: Insufficient DRAM address validation in System Management Unit (SMU) may allow an attacker to read/write from/to an invalid DRAM address, po

Noroxi assessment

Priority: Monitor (action score 30/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.50% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: kernel-firmware (openSUSE:Leap 15.5) 20230724-150500.3.9.1; kernel-firmware (openSUSE:Leap Micro 5.3) 20220509-150400.4.25.1; kernel-firmware (SUSE:Linux Enterprise High Performance Computing 15 SP1-LTSS) 20200107-150100.3.40.1.

Low priority for now. Upgrade to kernel-firmware (openSUSE:Leap 15.5) 20230724-150500.3.9.1; kernel-firmware (openSUSE:Leap Micro 5.3) 20220509-150400.4.25.1; kernel-firmware (SUSE:Linux Enterprise High Performance Computing 15 SP1-LTSS) 20200107-150100.3.40.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Insufficient 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.

HighCVSS 7.5 · v3.1—No exploit Fix available
Published
Nov 14, 2023
Updated
Jun 17, 2026
EPSS
0.5% · 43th percentile
CWE
—

Report tools

JSON

Action score

30

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.5%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.5
CNA · AMD
6.7
0.8 point gap

CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:L/I:H/A:L

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2021-46774

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
amdepyc 7001 firmware
amdepyc 7001
amdepyc 7251 firmware
amdepyc 7251
amdepyc 7261 firmware
amdepyc 7261
amdepyc 7281 firmware
amdepyc 7281
amdepyc 7301 firmware
amdepyc 7301
amdepyc 7351 firmware
amdepyc 7351

and 188 more

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • amd epyc 7001 firmwarebefore naplespi_1.0.0.k
  • amd epyc 7203 firmwarebefore milanpi_1.0.0.b
  • amd epyc 7203p firmwarebefore milanpi_1.0.0.b
  • amd epyc 7232p firmwarebefore romepi_1.0.0.g
  • amd epyc 7251 firmwarebefore naplespi_1.0.0.k
  • amd epyc 7252 firmwarebefore romepi_1.0.0.g
  • amd epyc 7261 firmwarebefore naplespi_1.0.0.k
  • amd epyc 7262 firmwarebefore romepi_1.0.0.g
  • amd epyc 7272 firmwarebefore romepi_1.0.0.g
  • amd epyc 7281 firmwarebefore naplespi_1.0.0.k
  • amd epyc 7282 firmwarebefore romepi_1.0.0.g
  • amd epyc 72f3 firmwarebefore milanpi_1.0.0.b
  • amd epyc 7301 firmwarebefore naplespi_1.0.0.k
  • amd epyc 7302 firmwarebefore romepi_1.0.0.g
  • amd epyc 7302p firmwarebefore romepi_1.0.0.g
  • amd epyc 7303 firmwarebefore milanpi_1.0.0.b
  • amd epyc 7303p firmwarebefore milanpi_1.0.0.b
  • amd epyc 7313 firmwarebefore milanpi_1.0.0.b
  • amd epyc 7313p firmwarebefore milanpi_1.0.0.b
  • amd epyc 7343 firmwarebefore milanpi_1.0.0.b

Versions reported by the vendor

Affected version ranges reported by the assigning authority (AMD). Independent of NVD's CPE analysis and usually ahead of it.

  • AMD 1st Gen AMD EPYC™ Processors

    • variousaffected
  • AMD 2nd Gen AMD EPYC™ Processors

    • variousaffected
  • AMD 3rd Gen AMD EPYC™ Processors

    • variousaffected
  • AMD 4th Gen AMD EPYC™ Processors

    • variousaffected
  • AMD AMD EPYC™ Embedded 3000

    • various, variousaffected
  • AMD AMD EPYC™ Embedded 7002

    • various, variousaffected
  • AMD AMD EPYC™ Embedded 7003

    • various, variousaffected
  • AMD AMD Ryzen™ Embedded 5000

    • variousaffected
  • AMD AMD Ryzen™ 5000 Series Desktop Processors “Vermeer”

    • variousaffected
  • AMD AMD Ryzen™ Threadripper™ 3000 Series Processors “Castle Peak” HEDT

    • variousaffected
  • AMD AMD Ryzen™ Threadripper™ PRO 3000WX Series Processors “Chagall” WS

    • variousaffected
  • AMD AMD Ryzen™ Threadripper™ PRO Processors “Castle Peak” WS SP3

    • variousaffected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
openSUSE:Leap 15.5kernel-firmwarebefore 20230724-150500.3.9.120230724-150500.3.9.1
openSUSE:Leap Micro 5.3kernel-firmwarebefore 20220509-150400.4.25.120220509-150400.4.25.1
SUSE:Linux Enterprise High Performance Computing 15 SP1-LTSSkernel-firmwarebefore 20200107-150100.3.40.120200107-150100.3.40.1
SUSE:Linux Enterprise High Performance Computing 15 SP3-ESPOSkernel-firmwarebefore 20210208-150300.4.19.120210208-150300.4.19.1
SUSE:Linux Enterprise Micro 5.3kernel-firmwarebefore 20220509-150400.4.25.120220509-150400.4.25.1
SUSE:Linux Enterprise Micro 5.5kernel-firmwarebefore 20230724-150500.3.9.120230724-150500.3.9.1
SUSE:Linux Enterprise Server 12 SP5kernel-firmwarebefore 20190618-5.34.120190618-5.34.1

Same product

amd: all records

Other highest-scoring records for the same primary product.

  • CVE-2021-26340A malicious hypervisor in conjunction with an unprivileged attacker process inside an SEV/SEV-ES guest VM may fail to flush the Translation
    33Monitor
  • CVE-2020-12988A potential denial of service (DoS) vulnerability exists in the integrated chipset that may allow a malicious attacker to hang the system wh
    30Monitor
  • CVE-2021-26356A TOCTOU in ASP bootloader may allow an attacker to tamper with the SPI ROM following data read to memory potentially resulting in S3 data c
    29Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2021-46744May 11, 2022 · An attacker with access to a malicious hypervisor may be able to infer data values used in a SEV guest on AMD CPUs by monitoring ciphertext
    26Monitor
  • ← EarlierCVE-2021-26403Jan 11, 2023 · Insufficient checks in SEV may lead to a malicious hypervisor disclosing the launch secret potentially resulting in compromise of VM confide
    26Monitor
  • Later →CVE-2023-20521Nov 14, 2023 · TOCTOU in the ASP Bootloader may allow an attacker with physical access to tamper with SPI ROM records after memory content verification, po
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
opensuse:kernel-firmware20230724-150500.3.9.1 · openSUSE:Leap 15.5Package registry (OSV)
suse:kernel-firmware20210208-150300.4.19.1 · SUSE:Linux Enterprise High Performance Computing 15 SP3-ESPOSPackage registry (OSV)
suse:kernel-firmware20230724-150500.3.9.1 · SUSE:Linux Enterprise Micro 5.5Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records