CVE-2024-57876drm/dp_mst: Fix resetting msg rx state after topology removal
- 7.0HighCVSS base score
- 0.16%Exploitation in 30 daysEPSS · top 94% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
Published
- 22 months later
· 22 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Modified | 3.1 | High7.0 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.16% · top 94% of all CVEs (18 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.0.
Affected products
- affected b30fcedeba643ca16eaa6212c1245598b7cd830d – < 94b33b2d7640e807869451384eb88321dd0ffbd4
- affected 1d082618bbf3b6755b8cc68c0a8122af2842d593 – < d834d20d2e86c52ed5cab41763fa61e6071680ef
- affected 1d082618bbf3b6755b8cc68c0a8122af2842d593 – < be826b4451fd187a7c0b04be4f8243d5df6e0450
- affected 1d082618bbf3b6755b8cc68c0a8122af2842d593 – < a6fa67d26de385c3c7a23c1e109a0e23bfda4ec7
- affected ee4a4282d78d96e07e714c28ca54679713fa2157
- affected db35e49413a4d03ea0c003598803e49956f59324
- affected a579ed4613b5a64074963988ad481e43cf3b917b
- affected 6.1.18 – < 6.1.120
- affected 5.10.173 – < 5.11
- affected 5.15.100 – < 5.16
- affected 6.2.5 – < 6.3
- affected 6.3
- unaffected < 6.3
- unaffected 6.1.120 – ≤ 6.1.*
- unaffected 6.6.66 – ≤ 6.6.*
- unaffected 6.12.5 – ≤ 6.12.*
- unaffected 6.13 – ≤ *
References
References5
- https://git.kernel.org/stable/c/94b33b2d7640e807869451384eb88321dd0ffbd4 (opens in a new tab)
- https://git.kernel.org/stable/c/d834d20d2e86c52ed5cab41763fa61e6071680ef (opens in a new tab)
- https://git.kernel.org/stable/c/be826b4451fd187a7c0b04be4f8243d5df6e0450 (opens in a new tab)
- https://git.kernel.org/stable/c/a6fa67d26de385c3c7a23c1e109a0e23bfda4ec7 (opens in a new tab)
- https://lists.debian.org/debian-lts-announce/2025/03/msg00001.html (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2024-53779 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2024-57876)Record last updated .