# CVE-2025-40332: drm/amdkfd: Fix mmap write lock not release

> A local attacker can trigger a deadlock in the Linux kernel's AMD GPU driver, causing a system hang and denial of service.

- **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:** 9 Dec 2025
- **Updated:** 23 May 2026
- **Also known as:** BELL-CVE-2025-40332, DEBIAN-CVE-2025-40332, GHSA-cqv3-6vqr-2pmm, ROOT-OS-DEBIAN-12-CVE-2025-40332, ROOT-OS-DEBIAN-13-CVE-2025-40332, ROOT-OS-UBUNTU-2204-CVE-2025-40332, ROOT-OS-UBUNTU-2404-CVE-2025-40332, UBUNTU-CVE-2025-40332

## What is CVE-2025-40332?

CVE-2025-40332 is a denial of service 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/amdkfd: Fix mmap write lock not release

If mmap write lock is taken while draining retry fault, mmap write lock
is not released because svm_range_restore_pages calls mmap_read_unlock
then returns. This causes deadlock and system hangs later because mmap
read or write lock cannot be taken.

Downgrade mmap write lock to read lock if draining retry fault fix this
bug.

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


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

Apply the vendor's patch.

## Is CVE-2025-40332 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-40332 is a denial of service 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-40332 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-40332/ (Markdown: https://insights.sbomify.com/CVE-2025-40332/index.md)
```

## Sources

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

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