drm/amdkfd: Destroy KFD debugfs after destroy KFD wq
Summary
| CVE | CVE-2025-39706 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2025-09-05 18:15:47 UTC |
| Updated | 2026-05-12 13:17:06 UTC |
| 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) |
Risk And Classification
Primary CVSS: v3.1 5.5 MEDIUM from [email protected]
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Problem Types: CWE-476
CVSS v3.1 Breakdown
Attack Vector
LocalAttack Complexity
LowPrivileges Required
LowUser Interaction
NoneScope
UnchangedConfidentiality
NoneIntegrity
NoneAvailability
HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Operating System | Linux | Linux Kernel | All | All | All | All |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 4a488a7ad71401169cecee75dc94bcce642e2c53 fc35c955da799ba62f6f977d58e0866d0251e3f8 git | Not specified |
| CNA | Linux | Linux | affected 4a488a7ad71401169cecee75dc94bcce642e2c53 74ee7445c3b61c3bd899a54bd82c1982cb3a8206 git | Not specified |
| CNA | Linux | Linux | affected 4a488a7ad71401169cecee75dc94bcce642e2c53 96609a51e6134542bf90e053c2cd2fe4f61ebce3 git | Not specified |
| CNA | Linux | Linux | affected 4a488a7ad71401169cecee75dc94bcce642e2c53 910735ded17cc306625e7e1cdcc8102f7ac60994 git | Not specified |
| CNA | Linux | Linux | affected 4a488a7ad71401169cecee75dc94bcce642e2c53 2e58401a24e7b2d4ec619104e1a76590c1284a4c git | Not specified |
| CNA | Linux | Linux | affected 3.19 | Not specified |
| CNA | Linux | Linux | unaffected 3.19 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.1.149 6.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.103 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.44 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.16.4 6.16.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.17 * original_commit_for_fix | Not specified |
| ADP | Siemens | SIMATIC CN 4100 | affected V5.0 custom | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/96609a51e6134542bf90e053c2cd2fe4f61ebce3 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| lists.debian.org/debian-lts-announce/2025/10/msg00008.html | af854a3a-2127-422b-91ae-364da2661108 | lists.debian.org | Mailing List, Third Party Advisory |
| git.kernel.org/stable/c/fc35c955da799ba62f6f977d58e0866d0251e3f8 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| cert-portal.siemens.com/productcert/html/ssa-032379.html | 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e | cert-portal.siemens.com | |
| git.kernel.org/stable/c/2e58401a24e7b2d4ec619104e1a76590c1284a4c | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/74ee7445c3b61c3bd899a54bd82c1982cb3a8206 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/910735ded17cc306625e7e1cdcc8102f7ac60994 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.