Vulnerability · Published Apr 17, 2024 · Assigned by Linux
CVE-2024-26916Revert "drm/amd: flush any delayed gfxoff on suspend entry"
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.2% (higher than 6% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
In the Linux kernel, the following vulnerability has been resolved: Revert "drm/amd: flush any delayed gfxoff on suspend entry" commit ab4750332dbe ("drm/amdgpu/sdma5.2: add begin/end_use ring callbacks") caused GFXOFF control to be used more heavily and the codepath that was removed from commit 0dee72639533 ("drm/amd: flush any delayed gfxoff on suspend entry") now can be exercised at suspend again. Users report that by using GNOME to suspend the lockscreen trigger will cause SDMA traffic and the system can deadlock. This reverts commit 0dee726395333fea833eaaf838bc80962df886c8.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.1.82-1 | DEBIAN-CVE-2024-26916 |
| Debian:13 | linux | 6.7.7-1 | DEBIAN-CVE-2024-26916 |
| Debian:14 | linux | 6.7.7-1 | DEBIAN-CVE-2024-26916 |
| Ubuntu:22.04:LTS | linux | 5.15.0-106.116 | UBUNTU-CVE-2024-26916 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2024-26916 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1061.67 | UBUNTU-CVE-2024-26916 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2024-26916 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2024-26916 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | 6.5.0-1023.23~22.04.1 | UBUNTU-CVE-2024-26916 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1063.72 | UBUNTU-CVE-2024-26916 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2024-26916 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2024-26916 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | 6.5.0-1024.25~22.04.1 | UBUNTU-CVE-2024-26916 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1063.72.1 | UBUNTU-CVE-2024-26916 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2024-26916 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2024-26916 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1059.67 | UBUNTU-CVE-2024-26916 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2024-26916 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2024-26916 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | 6.5.0-1024.26~22.04.1 | UBUNTU-CVE-2024-26916 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1058.63 | UBUNTU-CVE-2024-26916 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1044.51 | UBUNTU-CVE-2024-26916 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2024-26916 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2024-26916 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | 6.5.0-44.44~22.04.1 | UBUNTU-CVE-2024-26916 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1054.57 | UBUNTU-CVE-2024-26916 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1057.63 | UBUNTU-CVE-2024-26916 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1058.63 | UBUNTU-CVE-2024-26916 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-106.116 | UBUNTU-CVE-2024-26916 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2024-26916 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2024-26916 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | 6.5.0-44.44.1~22.04.1 | UBUNTU-CVE-2024-26916 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1054.55 | UBUNTU-CVE-2024-26916 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2024-26916 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | 6.5.0-1023.24 | UBUNTU-CVE-2024-26916 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2024-26916 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2024-26916 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2024-26916 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | 6.5.0-1027.28 | UBUNTU-CVE-2024-26916 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1059.65 | UBUNTU-CVE-2024-26916 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | 6.5.0-1026.26~22.04.1 | UBUNTU-CVE-2024-26916 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1054.57 | UBUNTU-CVE-2024-26916 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2024-26916 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2024-26916 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2024-26916 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2024-26916 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2024-26916 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2024-26916 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | 6.5.0-1017.18~22.04.1 | UBUNTU-CVE-2024-26916 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | f94942885e8416ce9de84d8fae93684002682b5d – before 65158edb0a3a8df23197d52cd24287e39eaf95d678b2ba39beef21c8baebb1868569c2026ad76de0 – before ff70e6ff6fc2413caf33410af7462d1f584d927e3aae4ef4d799fb3d0381157640fdb251008cf0ae – before caa2565a2e13899be31f7b1e069e6465d3e2adb0ab4750332dbe535243def5dcebc24ca00c1f98ac – before d855ceb6a5fde668c5431156bc60fae0cc52b764ab4750332dbe535243def5dcebc24ca00c1f98ac – before 916361685319098f696b798ef1560f69ed96e9345.15.144 – before 5.15.1496.1.69 – before 6.1.796.6.8 – before 6.6.18 |
| Linux | Linux | 6.7 |
References
- https://git.kernel.org/stable/c/65158edb0a3a8df23197d52cd24287e39eaf95d6
- https://git.kernel.org/stable/c/ff70e6ff6fc2413caf33410af7462d1f584d927e
- https://git.kernel.org/stable/c/caa2565a2e13899be31f7b1e069e6465d3e2adb0
- https://git.kernel.org/stable/c/d855ceb6a5fde668c5431156bc60fae0cc52b764
- https://git.kernel.org/stable/c/916361685319098f696b798ef1560f69ed96e934