dbcve.org
Integer OverflowWeakness · CWE-190

CVE-2024-36337

HIGH · 7.9 CVSS v3.1 Published 2025-04-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/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
Integer overflow within AMD NPU Driver could allow a local attacker to write out of bounds, potentially leading to loss of confidentiality, integrity or 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 confidence

Integer overflow vulnerability in AMD NPU (Neural Processing Unit) driver allows a local authenticated attacker to write beyond allocated memory boundaries, potentially achieving privilege escalation or causing system instability.

MitigationUpdate AMD NPU driver to the latest version provided by AMD once the patch is released. Apply operating system and platform security updates in conjunction with driver updates.

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/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 AMD NPU hardware presence
    Run 'lspci | grep -i neural' or check system information for AMD Neural Processing Unit device. On Windows, check Device Manager under 'Processors' or run 'msinfo32' for NPU information.
    Affected if System has AMD NPU hardware installed and is listed in PCI or system devices
  2. Check AMD NPU driver installation status
    On Linux, run 'lsmod | grep npu' or check /dev for npu devices. On Windows, open Device Manager, expand 'Processors', and look for AMD Neural Processors. Alternatively, run 'powershell Get-PnpDevice -Class Processor | Where-Object {$_.FriendlyName -match "NPU|Neural"}'
    Affected if AMD NPU driver is installed and the NPU device shows as active/enabled
  3. Retrieve installed NPU driver version
    On Windows, right-click the AMD NPU device in Device Manager, select Properties, go to Driver tab, and note the Driver Version. On Linux, check 'modinfo amd_npu' or examine /sys/class/npu/*/version if available. Also check AMD Adrenalin software if installed.
    Affected if Driver version can be retrieved and compared to the fixed version provided by AMD in their security advisory
  4. Verify NPU runtime state and accessibility
    Check if the NPU is currently powered on and accessible. On Linux, verify /dev/npu* exists and has proper permissions. On Windows, check if the NPU shows as 'This device is started' in Device Manager. Confirm the local authenticated user context has access.
    Affected if NPU is actively running and accessible to local authenticated users, making the integer overflow exploitable in the driver memory allocation routines
  5. Review system security logs for NPU-related events
    Check Windows Event Viewer under Application/System logs for amd*.sys or npu driver errors. On Linux, review 'dmesg | grep -i npu' or journalctl for NPU driver messages. Look for any memory allocation failures or driver warnings.
    Affected if NPU driver is actively loaded and handling operations, indicating the vulnerable code path could be reached

A user is affected if their system contains AMD NPU hardware, has the NPU driver installed and active, and the installed driver version is older than the fixed version AMD has released in their security advisory.

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

Update AMD NPU driver to the latest version provided by AMD once the patch is released. Apply operating system and platform security updates in conjunction with driver updates.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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