[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025121634-CVE-2025-68223-4e44@gregkh>
Date: Tue, 16 Dec 2025 14:57:42 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-68223: drm/radeon: delete radeon_fence_process in is_signaled, no deadlock
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
drm/radeon: delete radeon_fence_process in is_signaled, no deadlock
Delete the attempt to progress the queue when checking if fence is
signaled. This avoids deadlock.
dma-fence_ops::signaled can be called with the fence lock in unknown
state. For radeon, the fence lock is also the wait queue lock. This can
cause a self deadlock when signaled() tries to make forward progress on
the wait queue. But advancing the queue is unneeded because incorrectly
returning false from signaled() is perfectly acceptable.
(cherry picked from commit 527ba26e50ec2ca2be9c7c82f3ad42998a75d0db)
The Linux kernel CVE team has assigned CVE-2025-68223 to this issue.
Affected and fixed versions
===========================
Fixed in 6.12.60 with commit 73bc12d6a547f9571ce4393acfd73c004e2df9e5
Fixed in 6.17.10 with commit 7e3e9b3a44c23c8eac86a41308c05077d6d30f41
Fixed in 6.18 with commit 9eb00b5f5697bd56baa3222c7a1426fa15bacfb5
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2025-68223
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/gpu/drm/radeon/radeon_fence.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/73bc12d6a547f9571ce4393acfd73c004e2df9e5
https://git.kernel.org/stable/c/7e3e9b3a44c23c8eac86a41308c05077d6d30f41
https://git.kernel.org/stable/c/9eb00b5f5697bd56baa3222c7a1426fa15bacfb5
Powered by blists - more mailing lists