# CVE-2025-39706: drm/amdkfd: Destroy KFD debugfs after destroy KFD wq

> A null pointer dereference in the Linux kernel's AMD KFD driver causes a kernel hang when debugfs is destroyed prematurely.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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:** 5 Sep 2025
- **Updated:** 12 May 2026
- **Also known as:** AZL-66989, AZL-73725, BELL-CVE-2025-39706, DEBIAN-CVE-2025-39706, GHSA-8v4r-83gc-j76m, ROOT-OS-DEBIAN-11-CVE-2025-39706, ROOT-OS-DEBIAN-12-CVE-2025-39706, ROOT-OS-DEBIAN-13-CVE-2025-39706, ROOT-OS-UBUNTU-2204-CVE-2025-39706, ROOT-OS-UBUNTU-2404-CVE-2025-39706, UBUNTU-CVE-2025-39706

## What is CVE-2025-39706?

CVE-2025-39706 is a medium-severity vulnerability in Debian Debian Linux, published on 5 Sep 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: Destroy KFD debugfs after destroy KFD wq

Since KFD proc content was moved to kernel debugfs, we can't destroy KFD
debugfs before kfd_process_destroy_wq. Move kfd_process_destroy_wq prior
to kfd_debugfs_fini to fix a kernel NULL pointer problem. It happens
when /sys/kernel/debug/kfd was already destroyed in kfd_debugfs_fini but
kfd_process_destroy_wq calls kfd_debugfs_remove_process. This line
    debugfs_remove_recursive(entry->proc_dentry);
tries to remove /sys/kernel/debug/kfd/proc/<pid> while
/sys/kernel/debug/kfd is already gone. It hangs the kernel by kernel
NULL pointer.

(cherry picked from commit 0333052d90683d88531558dcfdbf2525cc37c233)

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 2 products.


Products: Debian Debian Linux, Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2025-39706 being exploited?

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

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-39706 is a medium-severity vulnerability in Debian Debian Linux, published on 5 Sep 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-39706 in the wild and no public exploit code.

Affected product: Debian Debian 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-39706/ (Markdown: https://insights.sbomify.com/CVE-2025-39706/index.md)
```

## Sources

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

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