dbcve.org
Integer OverflowWeakness · CWE-190

CVE-2024-36320

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 →
72/100
Remediation priority · Elevated
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 atihdwt6.sys can allow a local attacker to cause out of bound read/write potentially leading to loss of confidentiality, integrity and 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

A vulnerability exists in the atihdwt6.sys kernel-mode driver (associated with AMD/ATI graphics hardware) where an integer overflow can be exploited by a local attacker to perform out-of-bounds memory read/write operations, potentially compromising system confidentiality, integrity, and availability.

MitigationApply the vendor-supplied driver update/patch for atihdwt6.sys from AMD to address the integer overflow vulnerability; verify the update does not introduce compatibility issues with dependent software.

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
None
Scope
X

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/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. Locate the atihdwt6.sys driver file
    Search for atihdwt6.sys on the system using file search or command: Get-ChildItem -Path C:\Windows\System32\drivers -Filter atihdwt6.sys -Recurse -ErrorAction SilentlyContinue
    Affected if The driver file does not exist on the system (not vulnerable as the driver is not installed)
  2. Retrieve the driver file version
    Right-click the atihdwt6.sys file, select Properties, then view the Details tab to see the File Version, or run: (Get-Item 'C:\Windows\System32\drivers\atihdwt6.sys').VersionInfo
    Affected if The driver is present but no patched version information is available for comparison (user must verify against AMD release notes)
  3. Check if the driver is currently loaded
    Run: Get-Process -Name * | Where-Object {$_.Modules.ModuleName -eq 'atihdwt6.sys'} or check driver loaded status via: driverquery /v | findstr atihdwt6
    Affected if The driver is loaded and running in kernel mode (required condition for exploitation)
  4. Review driver signing status
    Run: signtool verify /v /pa C:\Windows\System32\drivers\atihdwt6.sys to verify digital signature validity
    Affected if The driver is unsigned or has an invalid signature (may indicate tampered or outdated driver)

The system is affected if the atihdwt6.sys driver is present and loaded, and the installed version has not been patched by AMD to address the integer overflow vulnerability.

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-supplied driver update/patch for atihdwt6.sys from AMD to address the integer overflow vulnerability; verify the update does not introduce compatibility issues with dependent software.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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