Vulnerability · Published Mar 26, 2024 · Assigned by Linux

CVE-2023-52625drm/amd/display: Refactor DMCUB enter/exit idle interface

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 10% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS NVD)5.5Medium
Exploit odds (30 days)0.2%top 90.0% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Refactor DMCUB enter/exit idle interface [Why] We can hang in place trying to send commands when the DMCUB isn't powered on. [How] We need to exit out of the idle state prior to sending a command, but the process that performs the exit also invokes a command itself. Fixing this issue involves the following: 1. Using a software state to track whether or not we need to start the process to exit idle or notify idle. It's possible for the hardware to have exited an idle state without driver knowledge, but entering one is always restricted to a driver allow - which makes the SW state vs HW state mismatch issue purely one of optimization, which should seldomly be hit, if at all. 2. Refactor any instances of exit/notify idle to use a single wrapper that maintains this SW state. This works simialr to dc_allow_idle_optimizations, but works at the DMCUB level and makes sure the state is marked prior to any notify/exit idle so we don't enter an infinite loop. 3. Make sure we exit out of idle prior to sending any commands or waiting for DMCUB idle. This patch takes care of 1/2. A future patch will take care of wrapping DMCUB command submission with calls to this new interface.

Affected packages & fixed versions

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

Affected products (as reported)

VendorProductVersions
Linux Linux 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c – before 820c3870c491946a78950cdf961bf40e28c1025f4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c – before 8e57c06bf4b0f51a4d6958e15e1a99c9520d00fa
Linux Linux 4.15

References