dbcve.org
UprofApplication · Amd

CVE-2025-48510

HIGH · 7.1 CVSS v3.1 Published 2025-11-24
Fix available
A fix is available. Upgrade to 5.0.1174 / 5.0.1223 or later.
See remediation →
73/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper return value within AMD uProf can allow a local attacker to bypass KSLR, potentially resulting in loss of confidentiality or availability.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

AMD uProf contains an improper return value flaw that allows a local attacker to bypass Kernel Space Layout Randomization (KSLR), potentially exposing kernel memory addresses and leading to loss of confidentiality or availability.

MitigationApply the vendor-supplied patch or update AMD uProf to the latest version to remediate this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
UprofApplication
Affected:< 5.0.1174< 5.0.1223< 5.0.1479

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if AMD uProf is installed
    Locate the uProf installation. Common paths: Windows - C:\Program Files\AMD\uProf\ or C:\Program Files\AMD\uProf\bin\uprof.exe; Linux - /opt/amuprof/ or /usr/local/amuprof/. Run 'where uprof' (Windows) or 'which uprof' (Linux) to find the executable.
    Affected if AMD uProf executable is found on the system
  2. Get the installed version number
    Run 'uprof -version' or 'uprof --version' from the command line, or check the file properties of uprof.exe. On Windows, you can also check 'uprof.exe' properties in the installation folder for version details.
    Affected if Unable to determine version or version field is empty
  3. Compare against affected version ranges
    Compare your installed version to the affected ranges: < 5.0.1174, < 5.0.1223, < 5.0.1479. Note which OS platform your installation is for, as different platforms may have different version branches.
    Affected if Installed version is lower than any of the listed fixed versions (5.0.1174, 5.0.1223, or 5.0.1479 depending on your platform)
  4. Confirm the vulnerable component is present
    Verify the main uProf driver or service components are installed. On Windows check for 'UPROF.sys' in the driver folder; on Linux check for loaded kernel modules related to uProf. The vulnerability affects the profiling driver component.
    Affected if The uProf driver component is installed and loaded on the system

You are affected if AMD uProf is installed and the installed version is lower than the fixed versions for your platform, as the improper return value flaw exists in the profiling driver that handles KSLR bypass.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.0.1174 / 5.0.1223 / 5.0.1479 or later
Fixed in 5.0.11745.0.12235.0.1479
Interim mitigation

Apply the vendor-supplied patch or update AMD uProf to the latest version to remediate this vulnerability.

Recommended fix Moderate confidence

AMD uProf version 5.0.1479 (or platform-specific: 5.0.1174 or 5.0.1223)

  1. 1. Identify the current installed version of AMD uProf by running 'uprof --version' or checking the installed package.
  2. 2. Determine which platform/branch of uProf is in use (the three version numbers suggest different platform-specific releases).
  3. 3. Download the fixed version from AMD's official website (www.amd.com) - look for uProf version 5.0.1479 or the appropriate branch-specific fixed release (5.0.1174 or 5.0.1223 depending on your platform).
  4. 4. Back up any existing profiling data or custom configurations if desired.
  5. 5. Install the fixed version following AMD's standard installation procedure for uProf.
  6. 6. Verify the new version is installed correctly using 'uprof --version'.
  7. 7. Test that uProf functions normally with a simple profiling command to confirm the fix does not introduce regressions.
Caveat Review AMD uProf release notes for version 5.0.x for any feature changes or migration requirements before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Uprof Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-48510 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-48510 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data