Independent & educational platform Not a government body. No link or affiliation with any government organisation. Made for learning only. Test only systems you own or are authorised to test. Become a Partner or Sponsor → Full disclaimer

CVE-2024-57876

high

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 remo…

Vendor / product: Linux — linux kernel

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.

CVSS
7.0
7.0 (CVSS v3.1)
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Severity source: NVD CVSS v3.1 (nvd@nist.gov)
Timeline (UTC)
Published: 2025-01-11 15:15
Modified: 2026-11-05 21:17
NVD status: Modified
Last synced 1 week ago
Verified against the source API 2026-11-05 21:23 UTC
Exploitation
Not listed in CISA KEV (as of last catalog sync)
Absence from KEV does not mean a CVE is not exploited. Exploitation status: unknown (no authoritative evidence in our sources).

Affected products

linux / linux_kernel ≥5.10.173 <5.11, ≥5.15.100 <5.16, ≥6.1.18 <6.1.120, ≥6.2.5 <6.6.66, ≥6.7 <6.12.5, 6.13

Weakness classification (CWE)

Source: NVD / CISA. “NVD-CWE-Other” and “NVD-CWE-noinfo” mean NVD could not assign a specific weakness.

Mitigation & advisories

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

References

Data sources

NVD CVE API 2.0 — fetched 2026-11-05 21:23 UTC · record ↗

Learn the basics

Understanding CVEs and CVSS Scores

Related CVEs