Log in Start free

Vulnerability · Published Feb 26, 2025 · Assigned by Linux

CVE-2022-49133drm/amdkfd: svm range restore work deadlock when process exit

Medium 5.5

In plain English

A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 19% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS NVD)5.5Medium
Exploit odds (30 days)0.3%top 81.4% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: svm range restore work deadlock when process exit kfd_process_notifier_release flush svm_range_restore_work which calls svm_range_list_lock_and_flush_work to flush deferred_list work, but if deferred_list work mmput release the last user, it will call exit_mmap -> notifier_release, it is deadlock with below backtrace. Move flush svm_range_restore_work to kfd_process_wq_release to avoid deadlock. Then svm_range_restore_work take task->mm ref to avoid mm is gone while validating and mapping ranges to GPU. Workqueue: events svm_range_deferred_list_work [amdgpu] Call Trace: wait_for_completion+0x94/0x100 __flush_work+0x12a/0x1e0 __cancel_work_timer+0x10e/0x190 cancel_delayed_work_sync+0x13/0x20 kfd_process_notifier_release+0x98/0x2a0 [amdgpu] __mmu_notifier_release+0x74/0x1f0 exit_mmap+0x170/0x200 mmput+0x5d/0x130 svm_range_deferred_list_work+0x104/0x230 [amdgpu] process_one_work+0x220/0x3c0

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linux5.17.3-1DEBIAN-CVE-2022-49133
Debian:13linux5.17.3-1DEBIAN-CVE-2022-49133
Debian:14linux5.17.3-1DEBIAN-CVE-2022-49133
Ubuntu:22.04:LTSlinuxno fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-awsno fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-azureno fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-intel-iotgno fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-kvmno fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-nvidia-tegra-igxno fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-raspino fix listedUBUNTU-CVE-2022-49133
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2022-49133
Ubuntu:22.04:LTSlinux-xilinx-zynqmpno fix listedUBUNTU-CVE-2022-49133

Affected products (as reported)

VendorProductVersions
Linux Linux 8a7c184a16d73ab25360e0f5997f82306ff5d5a2 – before a6be83086e91891081e0589e4b4645bf4643e8978a7c184a16d73ab25360e0f5997f82306ff5d5a2 – before 858822905f4bf44100d63c5e22e263109976f7cb8a7c184a16d73ab25360e0f5997f82306ff5d5a2 – before 6225bb3a88d22594aacea2485dc28ca12d596721
Linux Linux 5.14

References