CVE-2025-0014
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 · uneditedIncorrect default permissions on the AMD Ryzen(TM) AI installation folder could allow an 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 · high confidenceThe AMD Ryzen AI software installation folder has overly permissive default access controls that allow standard users to modify executable files or configurations within the program directory. A local attacker with standard user access could replace or modify files in this location to achieve elevation of privileges to administrator or SYSTEM level, enabling arbitrary code execution.
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
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/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.
-
Locate AMD Ryzen AI installation directoryCheck typical installation paths: C:\Program Files\AMD\Ryzen AI, C:\Program Files (x86)\AMD\Ryzen AI, or C:\Program Files\AMD\AMD Ryzen AI. Also search for folders named 'Ryzen AI' under Program Files using dir /s /b 'C:\Program Files\*Ryzen AI*' or check Registry key HKLM\SOFTWARE\AMD\RyzenAI for InstallPath.Affected if The installation directory exists on the system.
-
Check folder permissions on the Ryzen AI directoryRight-click the identified Ryzen AI installation folder, select Properties, go to the Security tab, and examine the permissions for Users or Standard Users group. Alternatively, use icacls 'C:\Path\To\RyzenAI' from an elevated command prompt to view effective permissions.Affected if The Users group or standard user accounts are granted Write or Modify permissions to the folder.
-
Verify executable file permissionsRun icacls 'C:\Path\To\RyzenAI\*.exe' to list permissions on executable files in the directory. Check if the Users group has (F) Full control or (M) Modify rights on .exe files.Affected if Standard users can modify or replace executable files in the Ryzen AI folder.
-
Check configuration file permissionsRun icacls 'C:\Path\To\RyzenAI\*.exe.config' or icacls on any .dll, .config, .json, or .xml files in the installation folder. Examine if Users group has write access.Affected if Standard users have write access to configuration files that could be modified for privilege escalation.
A user is affected if the AMD Ryzen AI installation directory grants Write or Modify permissions to standard (non-admin) users on executable or configuration files.
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.
From vendor dataRestrict folder permissions on the AMD Ryzen AI installation directory to prevent standard users from having write/modify access. Apply least-privilege principles, granting only read and execute permissions to non-admin users.
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0014 — 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-0014 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