[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025072521-CVE-2025-38410-e0e7@gregkh>
Date: Fri, 25 Jul 2025 15:20:24 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-38410: drm/msm: Fix a fence leak in submit error path
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
drm/msm: Fix a fence leak in submit error path
In error paths, we could unref the submit without calling
drm_sched_entity_push_job(), so msm_job_free() will never get
called. Since drm_sched_job_cleanup() will NULL out the
s_fence, we can use that to detect this case.
Patchwork: https://patchwork.freedesktop.org/patch/653584/
The Linux kernel CVE team has assigned CVE-2025-38410 to this issue.
Affected and fixed versions
===========================
Fixed in 5.15.187 with commit 5deab0fa6cfd0cd7def17598db15ceb84f950584
Fixed in 6.1.144 with commit 201eba5c9652a900c0b248070263f9acd3735689
Fixed in 6.6.97 with commit fe2695b2f63bd77e0e03bc0fc779164115bb4699
Fixed in 6.12.37 with commit 0eaa495b3d5710e5ba72051d2e01bb28292c625c
Fixed in 6.15.6 with commit 0dc817f852e5f8ec8501d19ef7dcc01affa181d0
Fixed in 6.16-rc3 with commit 5d319f75ccf7f0927425a7545aa1a22b3eedc189
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-38410
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/5deab0fa6cfd0cd7def17598db15ceb84f950584
https://git.kernel.org/stable/c/201eba5c9652a900c0b248070263f9acd3735689
https://git.kernel.org/stable/c/fe2695b2f63bd77e0e03bc0fc779164115bb4699
https://git.kernel.org/stable/c/0eaa495b3d5710e5ba72051d2e01bb28292c625c
https://git.kernel.org/stable/c/0dc817f852e5f8ec8501d19ef7dcc01affa181d0
https://git.kernel.org/stable/c/5d319f75ccf7f0927425a7545aa1a22b3eedc189
Powered by blists - more mailing lists