CVE-2025-48510
CVE-2025-48510 is a high-severity vulnerability in Amd Uprof with a CVSS 3.x base score of 7.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-394.
Key facts
- Severity: High (CVSS 3.x base score 7.1)
- EPSS exploit prediction: 0% (2nd percentile)
- Actively exploited: Not listed in CISA KEV
- EU (EUVD) id: EUVD-2025-198996
- Weakness: CWE-394
- Affected product: Amd Uprof
- Published:
- Last modified:
Description
Improper return value within AMD uProf can allow a local attacker to bypass KSLR, potentially resulting in loss of confidentiality or availability.
Frequently asked questions
- What is CVE-2025-48510?
- Improper return value within AMD uProf can allow a local attacker to bypass KSLR, potentially resulting in loss of confidentiality or availability.
- How severe is CVE-2025-48510?
- CVE-2025-48510 has a CVSS 3.x base score of 7.1, rated high severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability high.
- Is CVE-2025-48510 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (2nd percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2025-48510?
- CVE-2025-48510 primarily affects Amd Uprof. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
- How do I fix CVE-2025-48510?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
- Does CVE-2025-48510 have an EU (EUVD) identifier?
- Yes. CVE-2025-48510 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-198996.
- When was CVE-2025-48510 published?
- CVE-2025-48510 was published on 2025-11-24 and last updated on 2026-06-17.
References
Affected products (3)
- cpe:2.3:a:amd:uprof:*:*:*:*:*:windows:*:*
- cpe:2.3:a:amd:uprof:*:*:*:*:*:freebsd:*:*
- cpe:2.3:a:amd:uprof:*:*:*:*:*:linux:*:*
More vulnerabilities in Amd Uprof
- CVE-2023-31349 — High (CVSS 7.3): Incorrect default permissions in the AMD μProf installation directory could allow an attacker to achieve privilege…
- CVE-2023-31348 — High (CVSS 7.3): A DLL hijacking vulnerability in AMD μProf could allow an attacker to achieve privilege escalation, potentially…
- CVE-2023-31341 — High (CVSS 7.3): Insufficient validation of the Input Output Control (IOCTL) input buffer in AMD μProf may allow an authenticated…
- CVE-2024-36340 — Medium (CVSS 6.6): A junction point vulnerability within AMD uProf can allow a local low-privileged attacker to create junction points,…
- CVE-2026-28237 — Medium (CVSS 5.5): Unrestricted resource allocation in AMD uProf may be exploitable to consume excessive system resources, potentially…
- CVE-2026-0466 — Medium (CVSS 5.5): Improper access control in AMD uProf may allow a local attacker with user privileges to write to the kernel-shared…
All CVEs affecting Amd Uprof →
Other CWE-394 vulnerabilities
- CVE-2025-12516 — Critical (CVSS 9.8): Lack of Graceful Error Handling - HTTP 5xx ErrorThis issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5 .
- CVE-2025-12515 — Critical (CVSS 9.8): Systemic Internal Server Errors - HTTP 500 ResponseThis issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5 .
- CVE-2026-25085 — High (CVSS 8.6): A vulnerability exists in Copeland XWEB Pro version 1.12.1 and prior, in which an unexpected return value from the…
- CVE-2019-0066 — High (CVSS 7.5): An unexpected status return value weakness in the Next-Generation Multicast VPN (NG-mVPN) service of Juniper Networks…
- CVE-2025-23013 — High (CVSS 7.3): In Yubico pam-u2f before 1.3.1, local privilege escalation can sometimes occur. This product implements a Pluggable…
- CVE-2025-22854 — Medium (CVSS 6.9): Improper handling of non-200 http responses in the PingFederate Google Adapter leads to thread exhaustion under…