CVE-2024-36336
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 · uneditedInteger overflow within the AMD NPU Driver could allow a local attacker to write out of bounds, potentially leading to a 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 confidenceInteger overflow vulnerability in AMD NPU (Neural Processing Unit) driver allows a local attacker to perform out-of-bounds memory writes. The flaw exists in memory allocation/calculation logic within the driver, where integer overflow causes incorrect buffer size calculations leading to writes beyond allocated memory boundaries.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify AMD NPU hardware presenceRun 'lspci | grep -i neural' or check Device Manager under 'System devices' for AMD Neural Processing Unit, or run 'Get-PnpDevice -Class Processor -Status OK' on Windows and look for NPU entriesAffected if System has AMD NPU hardware installed ( Ryzen AI, AMD XDNA NPU, or similar)
-
Determine installed NPU driver versionOn Windows: open Device Manager, right-click the NPU device under 'System devices', select Properties > Driver tab, note the driver version. On Linux: run 'ls -la /dev/accel*' or check 'dmesg | grep -i npu' for driver load messages, or check '/sys/class/accel/accel*' for driver infoAffected if NPU driver is present and version is known (vulnerable versions would be specific to AMD's advisory)
-
Check for vulnerable memory allocation code pathInspect NPU driver files: on Windows check '%SystemRoot%\System32\drivers\amdnpu*.sys' file version and properties; on Linux check '/lib/modules/$(uname -r)/kernel/drivers/accel/amdnpu*' or similar driver pathsAffected if Vulnerable driver binary exists with the integer overflow in memory calculation routines
-
Verify local attacker contextReview system user accounts and privileges with 'who' or 'net user' on Windows, check if untrusted local users exist with interactive logon rights; verify if NPU driver services run with elevated privilegesAffected if Untrusted local users have access to the system (attacker needs local access to trigger the overflow)
System is affected if it contains AMD NPU hardware running an unpatched driver version where the integer overflow in memory allocation/calculation logic can be triggered by a local attacker.
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 dataApply AMD-provided driver updates for NPU hardware when released. Inventory systems with AMD NPU components and prioritize patching based on exposure. As a compensating control, restrict local access to trusted personnel only until official patches are available.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-36336 — 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-2024-36336 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