CVE-2025-48502
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 · uneditedImproper input validation within AMD uprof can allow a local attacker to overwrite MSR registers, potentially resulting in crash or denial of service.
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 confidenceAMD uprof contains improper input validation that allows a local attacker to supply crafted input to overwrite Model Specific Register (MSR) registers. This improper validation can lead to system instability, crashes, or denial of service.
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< 5.0.1174< 5.0.1223< 5.0.1479CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check if AMD uprof is installedSearch for the uprof utility on the system. Common locations include /usr/bin/uprof, /usr/local/bin/uprof, or check via 'which uprof' or 'find / -name uprof -type f 2>/dev/null'Affected if If the uprof executable exists on the system, proceed to version check
-
Identify the installed version of AMD uprofRun 'uprof --version' or 'uprof -v' to display the version number. If available, also check package manager listings (e.g., rpm -q uprof, dpkg -l uprof) for installed version detailsAffected if If no version output is returned, the tool may be installed but not functioning; treat as potentially affected
-
Compare version against affected rangesThe affected versions are: < 5.0.1174, < 5.0.1223, and < 5.0.1479. Compare your installed version number (e.g., 5.0.xxxx) against these thresholds. Note that versions 5.0.1479 and above are patched; versions below any of these three thresholds are vulnerableAffected if If the installed version is less than 5.0.1479 (or if version output shows any of the ranges < 5.0.1174, < 5.0.1223, < 5.0.1479), the system is affected by this vulnerability
The system is affected if AMD uprof is installed and the version number is lower than 5.0.1479.
Generated from the published advisory. Verify against your own configuration.
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 · scoped5.0.11745.0.12235.0.1479
Apply the vendor-provided patch/update for AMD uprof to remediate the input validation vulnerability. Until patched, limit local access to the uprof utility to trusted users only.
AMD uprof version 5.0.1479 or later
- Identify the current installed version of AMD uprof using 'uprof --version' or checking the installed package
- Download the latest AMD uporf version 5.0.1479 or later from the official AMD website at www.amd.com
- Stop any running profiling sessions or processes using uprof
- Uninstall the current version of AMD uprof using the appropriate package manager or installer
- Install the updated version 5.0.1479 or later
- Verify the installation by running 'uprof --version' to confirm the patched version is installed
- Restart any services or applications that use AMD uprof
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-48502 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-48502 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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