CVE-2021-46753Network attack vector

Protected-data exposure and corruption via unchecked header lengths

Published May 9, 2023 · Updated Jan 28, 2025

Improper input validation in AMD Ryzen and Athlon processor firmware allows attackers with a malicious UApp or ABL to corrupt protected data. The ASP sensor fusion hub header parser fails to validate length fields before mapping the hub region, allowing writes beyond intended data structures. Exploitation requires control of a UApp or AMD bootloader component and can expose or alter ASP-resident data, with no reported availability impact.

CVSS severity9.1
Critical
EPSS probability0.56%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper input validation in AMD Ryzen and Athlon processor firmware allows attackers with a malicious UApp or ABL to corrupt protected data. The ASP sensor fusion hub header parser fails to validate length fields before mapping the hub region, allowing writes beyond intended data structures. Exploitation requires control of a UApp or AMD bootloader component and can expose or alter ASP-resident data, with no reported availability impact.

The record

CVE
CVE-2021-46753
Published
May 9, 2023
Updated
Jan 28, 2025
Vendor
AMD
Product
Ryzen 5000 Series Mobile Processors with Radeon Graphics (Lucienne)
Classifications
Unavailable
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. May 9, 2023CVE publishedPublication date reported by the CVE source.
  2. Jan 28, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=various

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

AMD · Ryzen 5000 Series Mobile Processors with Radeon Graphics (Lucienne)version=various
AMD · Ryzen 2000 Series Mobile Processors (Raven Ridge, FP5)version=various
AMD · Ryzen 5000 Series Desktop Processors with Radeon Graphics (Cezanne, AM4)version=various
AMD · Athlon 3000 Series Mobile Processors with Radeon Graphics (Pollock)version=various
AMD · Athlon 3000 Series Mobile Processors with Radeon Graphics (Dali/Dali ULP)version=various
AMD · Ryzen 2000 Series Desktop Processors with Radeon Graphics (Raven Ridge, AM4)version=various
AMD · Ryzen 3000 Series Mobile Processors with Radeon Graphics (Renoir)version=various
AMD · Ryzen 5000 Series Mobile Processors with Radeon Graphics (Cezanne)version=various
AMD · Ryzen 6000 Series Mobile Processors (Rembrandt)version=various
AMD · Ryzen 3000 Series Mobile Processors with Radeon Graphics (Picasso)version=various

Published CVSS scores

9.1NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
9.1CISA-ADPCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

No sourced classifications are available.

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo