# CVE-2025-40334: drm/amdgpu: validate userq buffer virtual address and size

> A missing validation in the AMD GPU driver allows attackers to access invalid memory mappings, potentially leading to privilege escalation or code execution.

- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/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:** 9 Dec 2025
- **Updated:** 5 Aug 2026
- **Also known as:** BELL-CVE-2025-40334, DEBIAN-CVE-2025-40334, GHSA-qw3c-jf69-33ww, ROOT-OS-DEBIAN-12-CVE-2025-40334, ROOT-OS-DEBIAN-13-CVE-2025-40334, ROOT-OS-UBUNTU-2204-CVE-2025-40334, ROOT-OS-UBUNTU-2404-CVE-2025-40334, UBUNTU-CVE-2025-40334

## What is CVE-2025-40334?

CVE-2025-40334 is a high-severity missing authorization vulnerability in Linux, published on 9 Dec 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/amdgpu: validate userq buffer virtual address and size

It needs to validate the userq object virtual address to
determine whether it is residented in a valid vm mapping.

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


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

Apply the vendor's patch.

## Is CVE-2025-40334 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-40334 is a high-severity missing authorization vulnerability in Linux, published on 9 Dec 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-40334 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-40334/ (Markdown: https://insights.sbomify.com/CVE-2025-40334/index.md)
```

## Sources

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

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