dbcve.org
Out-of-bounds WriteWeakness · CWE-787

CVE-2025-48519

HIGH · 8.5 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 →
87/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
An improper input validation vulnerability within the AMD Platform Management Framework (PMF) driver can allow a local attacker to read or write Out-of-Bounds, potentially resulting in privilege escalation

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

The AMD Platform Management Framework (PMF) driver contains an improper input validation flaw that allows a local attacker to perform out-of-bounds memory read/write operations, potentially escalating privileges to kernel or system level.

MitigationApply AMD-provided patches for the PMF driver when released; if unavailable, evaluate disabling the PMF driver if functionality is not required, and restrict local system access to trusted administrators only.

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:H/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 if AMD PMF driver is installed
    Run 'driverquery /v | findstr -i PMF' or check Device Manager under System devices for 'AMD Platform Management Framework'
    Affected if The driver is present on the system
  2. Retrieve driver file version
    Locate the PMF driver file (typically amdpmf.sys in C:\Windows\System32\drivers\) and right-click Properties to view Version info, or run 'wmic path win32_pnpsigneddriver where "DeviceName like '%AMD PMF%'" get DeviceName,DriverVersion'
    Affected if A version number is returned
  3. Compare installed version to affected range
    Document the DriverVersion value and compare it against the official AMD security advisory version list once available; if no fixed version is published yet, note the current version for future comparison
    Affected if Installed version matches or predates the affected (unpatched) version range
  4. Verify driver is actively loaded
    Run 'sc query amdpmf' or check 'powershell Get-Service amdpmf' to see if the driver service is running
    Affected if Service state is RUNNING and driver is actively loaded in memory
  5. Check for recent driver activity or tampering
    Review Windows Event Viewer under System logs for Event ID 219 (Microsoft-Windows-DriverFrameworks-UserMode/Operational) or use 'powershell Get-WinEvent -FilterHashtable @{LogName='System';ID=219} -MaxEvents 50' looking for amdpmf.sys entries
    Affected if Unexpected driver load events or error patterns are present

The system is affected if the AMD PMF driver is installed and the installed version falls within the unpatched (vulnerable) version range or is unknown/unlisted in the AMD 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

Apply AMD-provided patches for the PMF driver when released; if unavailable, evaluate disabling the PMF driver if functionality is not required, and restrict local system access to trusted administrators only.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,260
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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