# CVE-2025-40110: drm/vmwgfx: Fix a null-ptr access in the cursor snooper

> A local attacker can cause a denial of service in the Linux kernel via a null pointer dereference in the vmwgfx cursor snooper.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Nov 2025
- **Updated:** 11 May 2026
- **Also known as:** AZL-69953, BELL-CVE-2025-40110, DEBIAN-CVE-2025-40110, GHSA-pvw2-x3cx-mv2h, ROOT-OS-DEBIAN-11-CVE-2025-40110, ROOT-OS-DEBIAN-12-CVE-2025-40110, ROOT-OS-DEBIAN-13-CVE-2025-40110, ROOT-OS-UBUNTU-2204-CVE-2025-40110, ROOT-OS-UBUNTU-2404-CVE-2025-40110, UBUNTU-CVE-2025-40110

## What is CVE-2025-40110?

CVE-2025-40110 is a vulnerability in Linux, published on 12 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

drm/vmwgfx: Fix a null-ptr access in the cursor snooper

Check that the resource which is converted to a surface exists before
trying to use the cursor snooper on it.

vmw_cmd_res_check allows explicit invalid (SVGA3D_INVALID_ID) identifiers
because some svga commands accept SVGA3D_INVALID_ID to mean "no surface",
unfortunately functions that accept the actual surfaces as objects might
(and in case of the cursor snooper, do not) be able to handle null
objects. Make sure that we validate not only the identifier (via the
vmw_cmd_res_check) but also check that the actual resource exists before
trying to do something with it.

Fixes unchecked null-ptr reference in the snooping code.

## Which versions are affected by CVE-2025-40110?


## How do I fix CVE-2025-40110?

Apply the vendor's patch.

## Is CVE-2025-40110 being exploited?

There is no known exploitation of CVE-2025-40110 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-40110 and fix it if it is affected.

What it is: CVE-2025-40110 is a vulnerability in Linux, published on 12 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-40110 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-40110/ (Markdown: https://insights.sbomify.com/CVE-2025-40110/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-40110
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-40110
- OSV: https://osv.dev/vulnerability/CVE-2025-40110

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-40110/
Summaries are generated and may contain mistakes; the official description above is the record.