Vulnerability · Published May 21, 2024 · Assigned by Linux
CVE-2023-52825drm/amdkfd: Fix a race condition of vram buffer unref in svm code
High 7.8
In plain English
A high-severity race condition 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.2% (higher than 8% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Fix a race condition of vram buffer unref in svm code prange->svm_bo unref can happen in both mmu callback and a callback after migrate to system ram. Both are async call in different tasks. Sync svm_bo unref operation to avoid random "use-after-free".
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.1.64-1 | DEBIAN-CVE-2023-52825 |
| Debian:13 | linux | 6.6.8-1 | DEBIAN-CVE-2023-52825 |
| Debian:14 | linux | 6.6.8-1 | DEBIAN-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux | 5.15.0-100.110 | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1056.61 | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1058.66 | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1058.66.1 | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1053.61 | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1052.57 | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1038.44 | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1048.51 | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1050.56 | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1052.57 | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-100.110 | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1046.46 | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | 6.5.0-1014.14 | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1025.25 | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1012.12 | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1053.59 | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1048.51 | UBUNTU-CVE-2023-52825 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2023-52825 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1030.34 | UBUNTU-CVE-2023-52825 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | e49fe4040a10c1cd3b215c511f658d15aa7c8be9 – before 7d43cdd22cd81a2b079e864c4321b9aba4c6af34e49fe4040a10c1cd3b215c511f658d15aa7c8be9 – before 50f35a907c4f9ed431fd3dbb8b871ef1cbb0718ee49fe4040a10c1cd3b215c511f658d15aa7c8be9 – before c772eacbd6d0845fc922af8716bb9d29ae27b8cfe49fe4040a10c1cd3b215c511f658d15aa7c8be9 – before fc0210720127cc6302e6d6f3de48f49c3fcf5659e49fe4040a10c1cd3b215c511f658d15aa7c8be9 – before 709c348261618da7ed89d6c303e2ceb9e453ba74 |
| Linux | Linux | 5.14 |
Weakness: CWE-362 · Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
References
- https://git.kernel.org/stable/c/7d43cdd22cd81a2b079e864c4321b9aba4c6af34
- https://git.kernel.org/stable/c/50f35a907c4f9ed431fd3dbb8b871ef1cbb0718e
- https://git.kernel.org/stable/c/c772eacbd6d0845fc922af8716bb9d29ae27b8cf
- https://git.kernel.org/stable/c/fc0210720127cc6302e6d6f3de48f49c3fcf5659
- https://git.kernel.org/stable/c/709c348261618da7ed89d6c303e2ceb9e453ba74