Skip to content
Fencer Vulns
critical 9.1

CVE-2021-46753 json

Failure to validate the length fields of the ASP (AMD Secure Processor) sensor fusion hub headers may allow an attacker with a malicious Ua…

published 2023-05-09 3 y ago modified 2026-06-17 4 mo ago also EUVD-2021-33409

cvss
9.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 46%
public exploits
0
none known

Summary

Failure to validate the length fields of the ASP (AMD Secure Processor) sensor fusion hub headers may allow an attacker with a malicious Uapp or ABL to map the ASP sensor fusion hub region and overwrite data structures leading to a potential loss of confidentiality and integrity.

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
total
Assessed
21 mo ago

Exploit prediction

0.56% chance of exploitation in the next 30 days, higher than 46% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CISA ADP 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
NVD 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
CNA 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected products

  • AMD Ryzen™ 2000 series Desktop Processors “Raven Ridge” AM4
  • AMD Ryzen™ 5000 Series Desktop processor with Radeon™ Graphics “Cezanne” AM4
  • AMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics “Dali”/”Dali” ULP
  • AMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics “Pollock”
  • AMD Ryzen™ 2000 Series Mobile Processors “Raven Ridge” FP5
  • AMD Ryzen™ 3000 Series Mobile processor, 2nd Gen AMD Ryzen™ Mobile Processors with Radeon™ Graphics “Picasso”
  • AMD Ryzen™ 3000 Series Mobile Processors with Radeon™ Graphics “Renoir”
  • AMD Ryzen™ 5000 Series Mobile Processors with Radeon™ Graphics “Lucienne”
  • AMD Ryzen™ 5000 Series Mobile processors with Radeon™ Graphics “Cezanne”
  • AMD Ryzen™ 6000 Series Mobile Processors "Rembrandt"

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.