dbcve.org
Classic Buffer OverflowWeakness · CWE-120

CVE-2025-29944

MEDIUM · 6.8 CVSS v4.0 Published 2026-05-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/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
A buffer overflow vulnerability within AMD Sensor Fusion Hub Driver can allow a local attacker to write out of bounds, potentially resulting in denial of service or crash

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 buffer overflow vulnerability in the AMD Sensor Fusion Hub Driver allows a local attacker to write out of bounds memory, potentially causing denial of service or system crash. This is a kernel-mode driver flaw affecting AMD processors' sensor hub functionality.

MitigationApply the vendor-provided security patch for the AMD Sensor Fusion Hub Driver once released; identify and inventory affected systems; test the update in a staging environment before production deployment to ensure sensor functionality is preserved.

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:N/VI:N/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. Identify AMD processor and sensor hub hardware
    Run 'wmic cpu get name,manufacturer' or check system information to confirm AMD processor. Check Device Manager under 'System devices' for 'AMD Sensor Fusion Hub' or similar sensor hub device.
    Affected if System has AMD processor with Sensor Fusion Hub hardware present
  2. Locate the AMD Sensor Fusion Hub driver file
    Search for driver files named 'AmdPSF.sys', 'AMDSensorFusionHub.sys', or similar in C:\Windows\System32\drivers\ and subdirectories. Use 'dir /s C:\Windows\System32\AmdPSF.sys' or 'Get-ChildItem -Path C:\Windows\System32 -Recurse -Filter *AmdPSF*'
    Affected if Driver file exists on the system
  3. Check driver file version
    Right-click the driver file, select Properties, then Details tab to view File Version. Alternatively run 'powershell (Get-Item 'C:\Windows\System32\drivers\AmdPSF.sys').VersionInfo'
    Affected if Driver version is present and lower than the patched version (compare against AMD security advisory once released)
  4. Verify driver is loaded in memory
    Run 'sc query AmdPSF' or check Device Manager driver status. In PowerShell: 'Get-Service -Name *AmdPSF*' or 'driverquery | findstr -i AmdPSF'
    Affected if Driver is currently running or loaded at startup
  5. Check for driver signing and loading status
    Run 'sigcheck -k AmdPSF' from Sysinternals or check driver signature status in Device Manager under driver details. Also check registry at HKLM\SYSTEM\CurrentControlSet\Services\AmdPSF for Start type.
    Affected if Driver is set to load (Start value 0-3) and is currently active

System is affected if it has an AMD processor with Sensor Fusion Hub hardware and the AmdPSF.sys driver is present and loaded at any version below the vendor-patched version.

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-provided security patch for the AMD Sensor Fusion Hub Driver once released; identify and inventory affected systems; test the update in a staging environment before production deployment to ensure sensor functionality is preserved.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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