[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025121655-CVE-2025-68314-847b@gregkh>
Date: Tue, 16 Dec 2025 16:39:57 +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-68314: drm/msm: make sure last_fence is always updated
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
drm/msm: make sure last_fence is always updated
Update last_fence in the vm-bind path instead of kernel managed path.
last_fence is used to wait for work to finish in vm_bind contexts but not
used for kernel managed contexts.
This fixes a bug where last_fence is not waited on context close leading
to faults as resources are freed while in use.
Patchwork: https://patchwork.freedesktop.org/patch/680080/
The Linux kernel CVE team has assigned CVE-2025-68314 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.17 with commit 92395af63a9958615edfa9d4ef1ea72c92a00410 and fixed in 6.17.8 with commit 8ee817ceafba266d9c6f3a09babd2ac7441d9a2b
Issue introduced in 6.17 with commit 92395af63a9958615edfa9d4ef1ea72c92a00410 and fixed in 6.18 with commit 86404a9e3013d814a772ac407573be5d3cd4ee0d
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-68314
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/msm/msm_gem_submit.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/8ee817ceafba266d9c6f3a09babd2ac7441d9a2b
https://git.kernel.org/stable/c/86404a9e3013d814a772ac407573be5d3cd4ee0d
Powered by blists - more mailing lists