drm/amdkfd: Destroy KFD debugfs after destroy KFD wq
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 2e58401a24e7b2d4ec619104e1a76590c1284a4c, Kernel 74ee7445c3b61c3bd899a54bd82c1982cb3a8206, Kernel 910735ded17cc306625e7e1cdcc8102f7ac60994 and 2 more.
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)
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =3.19, >=4a488a7ad71401169cecee75dc94bcce642e2c53 <2e58401a24e7b2d4ec619104e1a76590c1284a4c, >=4a488a7ad71401169cecee75dc94bcce642e2c53 <74ee7445c3b61c3bd899a54bd82c1982cb3a8206, >=4a488a7ad71401169cecee75dc94bcce642e2c53 <910735ded17cc306625e7e1cdcc8102f7ac60994, >=4a488a7ad71401169cecee75dc94bcce642e2c53 <96609a51e6134542bf90e053c2cd2fe4f61ebce3, >=4a488a7ad71401169cecee75dc94bcce642e2c53 <fc35c955da799ba62f6f977d58e0866d0251e3f8 | 2e58401a24e7b2d4ec619104e1a76590c1284a4c, 74ee7445c3b61c3bd899a54bd82c1982cb3a8206, 910735ded17cc306625e7e1cdcc8102f7ac60994, 96609a51e6134542bf90e053c2cd2fe4f61ebce3, fc35c955da799ba62f6f977d58e0866d0251e3f8 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket