UprofApplication · Amd
CVE-2026-0466
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 access control in AMD uProf may allow a local attacker with user privileges to write to the kernel-shared memory section, 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 · high confidenceImproper access control in AMD uProf allows a local attacker with standard user privileges to write to kernel-shared memory, potentially causing system 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
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.
-
Verify AMD uProf is installedCheck for AMD uProf installation using system package manager or by searching for uProf directories (e.g., /opt/amduprofile, Program Files/AMD uProf, or using 'dpkg -l | grep -i uprofile' or 'rpm -qa | grep -i uprofile' on Linux)Affected if AMD uProf is found installed on the system
-
Determine installed uProf versionRun the uProf version command (typically 'uprof --version' or check the product readme/install directory for version information) or query via package managerAffected if Installed version is lower than 5.3.518 (e.g., 5.3.x versions below 5.3.518, or earlier major versions)
-
Confirm the vulnerable component existsVerify the uProf profiler binaries and shared memory components are present on the system (look for updriver, umgr, or related kernel-shared memory modules in the uProf installation directory)Affected if The uProf profiler components are installed and accessible to standard users
The system is affected if AMD uProf is installed with a version lower than 5.3.518, as this allows local standard users to exploit improper access control in kernel-shared memory sections.
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 AMD uProf vendor patches when available; in the interim, restrict or disable AMD uProf for unprivileged users and monitor for suspicious access attempts.
AMD uProf 5.3.518 or later
- 1. Download AMD uProf version 5.3.518 or later from the official AMD website at www.amd.com/en/developer/uprof.html
- 2. Uninstall the current version of AMD uProf from the system
- 3. Install the new version (5.3.518 or later) following the installation prompts
- 4. Verify the installation by checking the installed version matches or exceeds 5.3.518
- 5. Restart any running instances of uProf to ensure the patched version is active
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Uprof
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0466 — 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-0466 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