dbcve.org
Ryzen Ai SoftwareApplication · Amd

CVE-2024-21975

HIGH · 7.8 CVSS v3.1 Published 2024-11-12
Fix available
A fix is available. Upgrade to 1.2 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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
Improper input validation in the NPU driver could allow an attacker to supply a specially crafted pointer potentially leading to 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

Improper input validation in the NPU (Neural Processing Unit) driver allows an attacker to supply a specially crafted pointer. This could enable arbitrary code execution in kernel/driver context, as the driver fails to properly validate user-supplied pointer values before using them.

MitigationApply vendor-provided security patches or firmware updates for the NPU driver. If no patch is available, consider disabling the NPU driver until a fix is released, or implement input validation hooks if the driver supports custom modifications.

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
Ryzen Ai SoftwareApplication
Affected:< 1.2

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if AMD Ryzen AI Software is installed
    Check the system for AMD Ryzen AI Software components. On Windows, look in Program Files/Program Files (x86) for 'AMD Ryzen AI' or 'AMD Software' directories. On Linux, check /opt or /usr/local/ for amd-ryzen-ai or similar directories. Also check installed programs list.
    Affected if The software is present on the system
  2. Determine the installed version of AMD Ryzen AI Software
    Locate version information in the installed software. Common locations include: the software's about/help dialog, README or CHANGELOG files in the installation directory, or the Windows registry under HKLM\SOFTWARE\AMD\RyzenAi. The version may also appear in the driver file properties of npu*.sys or similar NPU driver files.
    Affected if The version cannot be determined or the software is not installed - proceed with other checks
  3. Compare installed version to the affected range
    If a version is found, compare it numerically to version 1.2. Versions less than 1.0, 1.0.x, 1.1.x, and any version starting with 1.1 are all below 1.2 and considered affected.
    Affected if The installed version is less than 1.2 (e.g., 1.0, 1.1, 1.1.0, 0.x series)
  4. Verify if the NPU driver is enabled or loaded
    On Windows, check Device Manager under 'Processors' or 'System devices' for an AMD Neural Processing Unit device. Also check services (services.msc) for NPU-related services. On Linux, run 'lsmod' to check for npu or amd-npu kernel modules, or check /dev for npu device nodes.
    Affected if The NPU driver is present and enabled/loaded - the vulnerability requires the NPU driver to be active

A system is affected if AMD Ryzen AI Software version is below 1.2 AND the NPU driver is installed and enabled, as the improper pointer validation flaw only applies when the vulnerable driver is running.

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.

dbcve · scoped
Upgrade available Upgrade to 1.2 or later
Fixed in 1.2
Interim mitigation

Apply vendor-provided security patches or firmware updates for the NPU driver. If no patch is available, consider disabling the NPU driver until a fix is released, or implement input validation hooks if the driver supports custom modifications.

Recommended fix High confidence

Ryzen AI Software version 1.2

  1. Visit the official AMD website (www.amd.com) to locate the Ryzen AI Software download page
  2. Download Ryzen AI Software version 1.2 or later
  3. Follow AMD's standard installation procedure to update the NPU driver
  4. Restart the computer after installation to ensure the new driver is properly loaded

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ryzen Ai Software Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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