# CVE-2025-40111: drm/vmwgfx: Fix Use-after-free in validation

> A use-after-free flaw in the vmwgfx driver allows attackers to potentially execute code or escalate privileges via premature resource destruction.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 15 Oct 2026
- **Also known as:** AZL-69956, BELL-CVE-2025-40111, DEBIAN-CVE-2025-40111, GHSA-q6fq-7r5f-c3mx, ROOT-OS-DEBIAN-11-CVE-2025-40111, ROOT-OS-DEBIAN-13-CVE-2025-40111, ROOT-OS-UBUNTU-2404-CVE-2025-40111, UBUNTU-CVE-2025-40111

## What is CVE-2025-40111?

CVE-2025-40111 is a high-severity use after free 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 Use-after-free in validation

Nodes stored in the validation duplicates hashtable come from an arena
allocator that is cleared at the end of vmw_execbuf_process. All nodes
are expected to be cleared in vmw_validation_drop_ht but this node escaped
because its resource was destroyed prematurely.

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


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

Apply the vendor's patch.

## Is CVE-2025-40111 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-40111 is a high-severity use after free 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-40111 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-40111/ (Markdown: https://insights.sbomify.com/CVE-2025-40111/index.md)
```

## Sources

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

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