CVE-2024-57876: drm/dp_mst: Fix resetting msg rx state after topology removal

Severity: high (CVSS 7.0 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.2% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2025-01-11 · updated 2026-06-17
Weakness: CWE-362

Description

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 products

Linux kernel: from 5.10.173 before 5.11; from 5.15.100 before 5.16; from 6.1.18 before 6.1.120; from 6.2.5 before 6.6.66; from 6.7 before 6.12.5; 6.13-rc1 — fixed in 5.11, 5.16, 6.1.120, 6.12.5, 6.6.66

How to fix

Upgrade to a fixed version: Linux kernel 5.11, 5.16, 6.1.120, 6.12.5. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2024-57876 or the next vulnerability affects your stack