Home/CVE/A transient execution vulnerability within AMD CPUs may allow a local user-privileged attacker to leak data via the floa
CVE
CVE-2025-54505
A transient execution vulnerability within AMD CPUs may allow a local user-privileged attacker to leak data via the floa
A transient execution vulnerability within AMD CPUs may allow a local user-privileged attacker to leak data via the floating point divisor unit, potentially resulting in loss of confidentiality.
EPSS 0.00011
Schedule remediation
- Public exploit or PoC is available
- ⚠ NVD has not scored this CVE yet - manual triage required (common for recent CVEs)
Sigma rules0
YARA rules0
Look this up elsewhere - one-click external pivots
▸
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2025-54505, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked.
EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal.
CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score.
Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits.
PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
⚠
Public Exploits & PoCs
1These PoC and exploit links come from public sources and are not verified to be safe or functional. Review the code before running anything, and treat unverified entries as untrusted.
📦
Fixed versions by distribution
14The package version that resolves this CVE on each Linux distribution, from the vendor’s published security data. fixed in shows a patched version exists; open means the package is listed as affected with no fix yet.
alpine edgexen fixed in 4.21.1-r2
alpine v3.20xen fixed in 4.18.5-r6
suse sle15kernel-default open
suse sle15kernel-default-devel open
suse sle15kernel-devel open
suse sle15kernel-macros open
suse sle15kernel-source open
suse sle15reiserfs-kmp-default open
suse sle15xen fixed in 0:4.20.3_02-150700.3.33.1
suse sle15xen-devel fixed in 0:4.16.7_08-150400.4.81.2
suse sle15xen-libs fixed in 0:4.17.6_08-150500.3.65.1
suse sle15xen-tools fixed in 0:4.18.5_16-150600.3.45.1
suse sle15xen-tools-domU fixed in 0:4.16.7_08-150400.4.81.2
suse sle15xen-tools-xendomains-wait-disk fixed in 0:4.20.3_02-150700.3.33.1
▣
Scoring & Timeline
SSVC triage · cisa-vulnrichment
Exploitation
none
Automatable
no
Technical impact
partial
SSVC asks the questions that actually drive patch urgency: is it being exploited, can attacks be automated, and how total is the impact.
⚑
Vendor Advisories
6suse-csafSUSE-SU-2026:2102-1
suse-csafSUSE-SU-2026:2066-1
suse-csafSUSE-SU-2026:1743-1
suse-csafSUSE-SU-2026:1692-1
suse-csafSUSE-SU-2026:1657-1
🔗
References & Sources
2Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.