Skip to content
Fencer Intel
medium 5.3

CVE-2025-52534 json

Improper bound check within AMD CPU microcode can allow a malicious guest to write to host memory, potentially resulting in loss of integri…

published 8mo ago modified 4mo ago also EUVD-2025-207435

cvss
5.3
version 4.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 29%
public exploits
0
none known

Summary

Improper bound check within AMD CPU microcode can allow a malicious guest to write to host memory, potentially resulting in loss of integrity.

Patch / fix

  • AMD AMD EPYC™ 9005 Series Processors TurinPI 1.0.0.6
  • amd64-microcode Debian 14 3.20260923.1

debian advisories DEBIAN-CVE-2025-52534

  • amd64-microcode Ubuntu 24.04 LTS 3.20251202.1ubuntu0.24.04.1
  • amd64-microcode Ubuntu 25.10 3.20251202.1ubuntu0.25.10.1
  • amd64-microcode Ubuntu 26.04 LTS 3.20251202.1ubuntu1

ubuntu advisories UBUNTU-CVE-2025-52534

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2025-52534 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
8mo ago

Exploit prediction

0.35% chance of exploitation in the next 30 days, higher than 29% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 4.0 5.3 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N
CNA 4.0 5.3 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Affected products

  • AMD AMD EPYC™ 9005 Series Processors

Classification

Weakness
  • CWE-1284 Improper Validation of Specified Quantity in Input

References

Sources

Fencer Intel 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.