dbcve.org
Incorrect Permission AssignmentWeakness · CWE-732

CVE-2025-61969

HIGH · 7.0 CVSS v4.0 Published 2026-02-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated

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
Incorrect permission assignment in AMD µProf may allow a local user-privileged attacker to achieve privilege escalation, potentially resulting in arbitrary code execution.

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 µProf contains an incorrect permission assignment vulnerability where the software sets improper file or system permissions, allowing a local unprivileged user to escalate privileges to a higher level, potentially achieving arbitrary code execution on the affected system.

MitigationApply the vendor patch from AMD when available, or contact AMD support for the corrected permission configuration; remove or restrict access to AMD µProf installations if a patch is not yet available.

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

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
Authentication
X
User interaction
P
Scope
X

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 µProf is installed
    Search for AMD µProf installation directories. On Windows, check 'C:\Program Files\AMD\µProf' or 'C:\Program Files\AMD\APU_PROF'. On Linux, check '/opt/amd/uprof' or '/usr/local/amd/uprof'. Use commands: 'dir "C:\Program Files\AMD" /ad' (Windows) or 'ls -la /opt/amd/ 2>/dev/null || ls -la /usr/local/amd/ 2>/dev/null' (Linux).
    Affected if AMD µProf directory exists on the system
  2. Identify all executable files in the installation
    List all .exe, .dll, or binary files within the AMD µProf installation directory. On Windows: 'dir /s /b "C:\Program Files\AMD\*.*"'. On Linux: 'find /opt/amd/uprof -type f -executable 2>/dev/null'.
    Affected if Executable files are present in the µProf installation folder
  3. Verify file permissions on executables and binaries
    Check if files have overly permissive access. On Windows, use 'icacls "C:\Program Files\AMD\µProf\*"' to view permissions. On Linux, use 'ls -la /opt/amd/uprof/bin/' or 'namei -l /opt/amd/uprof/bin/*'. Look for 'Everyone', 'Users', or 'World' with Write or Modify permissions on executable files.
    Affected if Executable files grant write or modify access to unprivileged users (BUILTIN\Users or Everyone with Write/Modify permissions)
  4. Check permissions on configuration files
    Locate configuration or data files within the µProf directory. On Windows: 'dir /s /b "C:\Program Files\AMD\µProf\*.xml" "C:\Program Files\AMD\µProf\*.ini" "C:\Program Files\AMD\µProf\*.conf"'. On Linux: 'find /opt/amd/uprof -name "*.xml" -o -name "*.ini" -o -name "*.conf"'. Check permissions with 'icacls' (Windows) or 'ls -la' (Linux).
    Affected if Configuration files are world-writable or group-writable by non-admin users
  5. Check service or driver file permissions
    If AMD µProf installs as a Windows service or kernel driver, check permissions on related files in system directories. Use 'sc qc uprof' (if service name known) or search for 'uprof' in C:\Windows\System32. Check if these files allow modification by standard users.
    Affected if Service executables or driver files can be modified by unprivileged users

The system is affected if AMD µProf is installed and any of its executable, configuration, or service files have permissions allowing unprivileged users to write or modify them, enabling privilege escalation.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch from AMD when available, or contact AMD support for the corrected permission configuration; remove or restrict access to AMD µProf installations if a patch is not yet available.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-61969 — 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-61969 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