cbcvebase.
CVE-2024-57876
published 2025-01-11

CVE-2024-57876: In the Linux kernel, the following vulnerability has been resolved: drm/dp_mst: Fix resetting msg rx state after topology removal If the MST topology is…

PriorityP428high7CVSS 3.1
AVLACHPRLUINSUCHIHAH
EPSS
0.16%
5.5th percentile
In the Linux kernel, the following vulnerability has been resolved: drm/dp_mst: Fix resetting msg rx state after topology removal If the MST topology is removed during the reception of an MST down reply or MST up request sideband message, the drm_dp_mst_topology_mgr::up_req_recv/down_rep_recv states could be reset from one thread via drm_dp_mst_topology_mgr_set_mst(false), racing with the reading/parsing of the message from another thread via drm_dp_mst_handle_down_rep() or drm_dp_mst_handle_up_req(). The race is possible since the reader/parser doesn't hold any lock while accessing the reception state. This in turn can lead to a memory corruption in the reader/parser as described by commit bd2fccac61b4 ("drm/dp_mst: Fix MST sideband message body length check"). Fix the above by resetting the message reception state if needed before reading/parsing a message. Another solution would be to hold the drm_dp_mst_topology_mgr::lock for the whole duration of the message reception/parsing in drm_dp_mst_handle_down_rep() and drm_dp_mst_handle_up_req(), however this would require a bigger change. Since the fix is also needed for stable, opting for the simpler solution in this patch.

Affected

24 ranges
VendorProductVersion rangeFixed in
debianlinux< linux 6.1.123-1 (bookworm)linux 6.1.123-1 (bookworm)
debianlinux-6.1< linux 6.1.123-1 (bookworm)linux 6.1.123-1 (bookworm)
linuxlinux
linuxlinux
linuxlinux
linuxlinux
linuxlinux>= 1d082618bbf3b6755b8cc68c0a8122af2842d593 < d834d20d2e86c52ed5cab41763fa61e6071680efd834d20d2e86c52ed5cab41763fa61e6071680ef
linuxlinux>= 1d082618bbf3b6755b8cc68c0a8122af2842d593 < be826b4451fd187a7c0b04be4f8243d5df6e0450be826b4451fd187a7c0b04be4f8243d5df6e0450
linuxlinux>= 1d082618bbf3b6755b8cc68c0a8122af2842d593 < a6fa67d26de385c3c7a23c1e109a0e23bfda4ec7a6fa67d26de385c3c7a23c1e109a0e23bfda4ec7
linuxlinux>= 5.10.173 < 5.115.11
linuxlinux>= 5.15.100 < 5.165.16
linuxlinux>= 6.1.18 < 6.1.1206.1.120
linuxlinux>= 6.2.5 < 6.36.3
linuxlinux>= b30fcedeba643ca16eaa6212c1245598b7cd830d < 94b33b2d7640e807869451384eb88321dd0ffbd494b33b2d7640e807869451384eb88321dd0ffbd4
linuxlinux_kernel
linuxlinux_kernel>= 0 < 6.1.123-16.1.123-1
linuxlinux_kernel>= 0 < 6.12.5-16.12.5-1
linuxlinux_kernel>= 0 < 6.12.5-16.12.5-1
linuxlinux_kernel>= 0 < 6.8.0-58.606.8.0-58.60
linuxlinux_kernel>= 5.10.173 < 5.115.11
linuxlinux_kernel>= 5.15.100 < 5.165.16
linuxlinux_kernel>= 6.1.18 < 6.1.1206.1.120
linuxlinux_kernel>= 6.2.5 < 6.6.666.6.66
linuxlinux_kernel>= 6.7 < 6.12.56.12.5

CVSS provenance

nvdv3.17.0HIGHCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
osv8.8HIGH
vendor_ubuntu8.8HIGH
vendor_debian7.0HIGH
vendor_redhat7.0HIGH
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.