dbcve.org
Memory Buffer Bounds ErrorWeakness · CWE-119

CVE-2025-36510

MEDIUM · 6.8 CVSS v4.0 Published 2026-05-12
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
Improper buffer restrictions for some Display Virtualization for Windows OS driver software within Ring 2: Device Drivers may allow a denial of service. Unprivileged software adversary with an authenticated user combined with a low complexity attack may enable denial of service. This result may potentially occur via local access when attack requirements are not present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (none), integrity (none) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.

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 restriction vulnerability in Windows Display Virtualization drivers (Ring 2 device drivers) allows a local authenticated user with low complexity to cause denial of service via improper buffer handling, requiring no user interaction or special internal knowledge.

MitigationApply vendor-provided security patches for Windows Display Virtualization drivers through standard Windows Update or vendor-specific updates; prioritize systems running display virtualization 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: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 installed display virtualization software
    Review installed programs for known display virtualization solutions such as VMware Horizon, Citrix Virtual Desktop, Microsoft RemoteFX, VirtualBox with guest additions, or similar virtualization platforms. Check Program Files directories for related components.
    Affected if Display virtualization software or drivers are installed on the system
  2. Enumerate display virtualization Ring 2 drivers
    Open Device Manager, expand 'Display adapters' and 'System devices', and look for drivers related to virtualization (e.g., VMware SVGA, VirtualBox Graphics, Citrix Display Driver, Microsoft Basic Render Driver for virtualization). Run 'driverquery /v' and filter for virtualization-related drivers.
    Affected if Ring 2 display virtualization drivers are present in the device driver list
  3. Check driver file versions
    Right-click identified display virtualization drivers in Device Manager, select Properties, and review the Driver version and Driver date fields. Alternatively, use 'wmic path win32_pnpsigneddriver' to query driver versions programmatically.
    Affected if Driver versions cannot be compared to vendor patch levels or show unpatched versions
  4. Audit for virtual display endpoints
    Run 'Get-PnpDevice -Class Display' or check registry under HKLM\SYSTEM\CurrentControlSet\Services for display driver services with virtualization-related names. Look for active virtual display adapters.
    Affected if Virtual display adapters or drivers are enumerated as active in the system

A system is affected if it has Windows display virtualization Ring 2 drivers installed and running, particularly from platforms that have not received the CVE-2025-36510 security patches from their vendors.

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 vendor-provided security patches for Windows Display Virtualization drivers through standard Windows Update or vendor-specific updates; prioritize systems running display virtualization software.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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