| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.9 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in AMD μProf up to 4.x. The affected element is an unknown function of the component KSLR. The manipulation leads to status code. This vulnerability is traded as CVE-2025-48510. An attack has to be approached locally. There is no exploit available. It is suggested to upgrade the affected component.
Details
A vulnerability was found in AMD μProf up to 4.x. It has been rated as critical. This issue affects an unknown code of the component KSLR. The manipulation with an unknown input leads to a status code vulnerability. Using CWE to declare the problem leads to CWE-394. The product does not properly check when a function or operation returns a value that is legitimate for the function, but is not expected by the product. Impacted is confidentiality, and availability. The summary by CVE is:
Improper return value within AMD uProf can allow a local attacker to bypass KSLR, potentially resulting in loss of confidentiality or availability.
The advisory is shared at amd.com. The identification of this vulnerability is CVE-2025-48510 since 05/22/2025. The exploitation is known to be easy. An attack has to be approached locally. Neither technical details nor an exploit are publicly available.
Upgrading to version 5.0 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.1VulDB Meta Temp Score: 6.9
VulDB Base Score: 7.1
VulDB Temp Score: 6.8
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.1
CNA Vector (AMD): 🔒
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: Status codeCWE: CWE-394 / CWE-393
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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: μProf 5.0
Timeline
05/22/2025 CVE reserved11/25/2025 Advisory disclosed
11/25/2025 VulDB entry created
11/25/2025 VulDB entry last update
Sources
Advisory: amd.comStatus: Confirmed
CVE: CVE-2025-48510 (🔒)
GCVE (CVE): GCVE-0-2025-48510
GCVE (VulDB): GCVE-100-333449
Entry
Created: 11/25/2025 07:46Changes: 11/25/2025 07:46 (30), 11/25/2025 07:47 (33)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.