UprofApplication · Amd
CVE-2026-28237
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 · uneditedUnrestricted resource allocation in AMD uProf may be exploitable to consume excessive system resources, potentially leading to a loss of 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 confidenceAMD uProf contains an unrestricted resource allocation vulnerability that allows excessive consumption of system resources, potentially leading to denial of service. The vulnerability appears to stem from insufficient controls on resource allocation within the profiling software.
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
< 5.3.518CVSS 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 installedRun 'uprof --version' or 'uprof -v' from command line, or check installed programs via system package managerAffected if AMD uProf is present on the system
-
Identify installed AMD uProf version numberExecute 'uprof --version' and note the version string output, or look for version info in the installation directoryAffected if Version displayed is lower than 5.3.518
-
Confirm profiling tool is accessibleVerify the 'uprof' command or profiling binaries are executable and available to users on the systemAffected if Users can execute the profiling tool without additional configuration
-
Verify resource limits are not appliedCheck if OS-level resource limits (ulimit, cgroups, container limits) are configured to constrain CPU, memory, or file descriptor usage for the profiling toolAffected if No resource limits are in place to restrict AMD uProf resource consumption
The environment is affected if AMD uProf version is installed and is lower than 5.3.518, and the profiling tool can run without operating system resource constraints in place.
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.3.518
Apply vendor-supplied patches for AMD uProf when available; implement system-level resource monitoring and limits to mitigate potential exploitation until patches are applied.
AMD uProf version 5.3.518 or later
- Navigate to the AMD official website and locate the AMD uProf (AMD μProf) download page
- Download AMD uProf version 5.3.518 or the latest available version
- Close any running instances of AMD uProf
- Install the downloaded AMD uProf update following the installation wizard prompts
- Restart the system or restart any previously running AMD uProf instances
- Verify the installed version by checking the AMD uProf help/about section to confirm version 5.3.518 or later is running
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Uprof
Scoped from the published advisory
- 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-2026-28237 — 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-2026-28237 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