AMD EPYC 7001 Processors/EPYC Embedded 3000 Processors Floating Point information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.2 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in AMD EPYC 7001 Processors and EPYC Embedded 3000 Processors. Impacted is an unknown function of the component Floating Point Handler. The manipulation leads to information disclosure. This vulnerability is uniquely identified as CVE-2025-54505. Local access is required to approach this attack. No exploit exists. You should upgrade the affected component.
Details
A vulnerability was found in AMD EPYC 7001 Processors and EPYC Embedded 3000 Processors (affected version not known). It has been rated as problematic. This issue affects some unknown functionality of the component Floating Point Handler. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. The summary by CVE is:
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.
The advisory is shared at amd.com. The identification of this vulnerability is CVE-2025-54505 since 07/23/2025. The exploitation is known to be easy. An attack has to be approached locally. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
The vulnerability scanner Nessus provides a plugin with the ID 311366 (Fedora 43 : xen (2026-78cd69d9ae)), which helps to determine the existence of the flaw in a target environment.
Upgrading eliminates this vulnerability.
The vulnerability is also documented in the databases at Tenable (311366) and CERT Bund (WID-SEC-2026-1175). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- Fedora Linux
- SUSE Linux
- AMD Prozessor
- Open Source Xen
Product
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 3.3VulDB Meta Temp Score: 3.2
VulDB Base Score: 3.3
VulDB Temp Score: 3.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 311366
Nessus Name: Fedora 43 : xen (2026-78cd69d9ae)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Timeline
07/23/2025 CVE reserved04/27/2026 Advisory disclosed
04/27/2026 VulDB entry created
05/04/2026 VulDB entry last update
Sources
Advisory: amd.comStatus: Confirmed
CVE: CVE-2025-54505 (🔒)
GCVE (CVE): GCVE-0-2025-54505
GCVE (VulDB): GCVE-100-359837
CERT Bund: WID-SEC-2026-1175 - AMD Prozessoren und Xen: Schwachstelle ermöglicht Offenlegung von Informationen
Entry
Created: 04/27/2026 17:52Updated: 05/04/2026 00:37
Changes: 04/27/2026 17:52 (65), 05/01/2026 19:34 (2), 05/04/2026 00:37 (7)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.