[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025011151-CVE-2024-57798-68b5@gregkh>
Date: Sat, 11 Jan 2025 13:39:53 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2024-57798: drm/dp_mst: Ensure mst_primary pointer is valid in drm_dp_mst_handle_up_req()
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
drm/dp_mst: Ensure mst_primary pointer is valid in drm_dp_mst_handle_up_req()
While receiving an MST up request message from one thread in
drm_dp_mst_handle_up_req(), the MST topology could be removed from
another thread via drm_dp_mst_topology_mgr_set_mst(false), freeing
mst_primary and setting drm_dp_mst_topology_mgr::mst_primary to NULL.
This could lead to a NULL deref/use-after-free of mst_primary in
drm_dp_mst_handle_up_req().
Avoid the above by holding a reference for mst_primary in
drm_dp_mst_handle_up_req() while it's used.
v2: Fix kfreeing the request if getting an mst_primary reference fails.
The Linux kernel CVE team has assigned CVE-2024-57798 to this issue.
Affected and fixed versions
===========================
Fixed in 6.1.123 with commit f61b2e5e7821f868d6afc22382a66a30ee780ba0
Fixed in 6.6.69 with commit 9735d40f5fde9970aa46e828ecc85c32571d58a2
Fixed in 6.12.8 with commit ce55818b2d3a999f886af91679589e4644ff1dc8
Fixed in 6.13-rc2 with commit e54b00086f7473dbda1a7d6fc47720ced157c6a8
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-2024-57798
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/display/drm_dp_mst_topology.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/f61b2e5e7821f868d6afc22382a66a30ee780ba0
https://git.kernel.org/stable/c/9735d40f5fde9970aa46e828ecc85c32571d58a2
https://git.kernel.org/stable/c/ce55818b2d3a999f886af91679589e4644ff1dc8
https://git.kernel.org/stable/c/e54b00086f7473dbda1a7d6fc47720ced157c6a8
Powered by blists - more mailing lists