---
id: CVE-2024-57876
title: 'drm/dp_mst: Fix resetting msg rx state after topology removal'
summary: |-
  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 messa…
severity: none
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= b30fcedeba643ca16eaa6212c1245598b7cd830d <
    94b33b2d7640e807869451384eb88321dd0ffbd4
  - >-
    Linux >= 1d082618bbf3b6755b8cc68c0a8122af2842d593 <
    d834d20d2e86c52ed5cab41763fa61e6071680ef
  - >-
    Linux >= 1d082618bbf3b6755b8cc68c0a8122af2842d593 <
    be826b4451fd187a7c0b04be4f8243d5df6e0450
  - >-
    Linux >= 1d082618bbf3b6755b8cc68c0a8122af2842d593 <
    a6fa67d26de385c3c7a23c1e109a0e23bfda4ec7
  - Linux ee4a4282d78d96e07e714c28ca54679713fa2157
  - Linux db35e49413a4d03ea0c003598803e49956f59324
  - Linux a579ed4613b5a64074963988ad481e43cf3b917b
  - Linux >= 6.1.18 < 6.1.120
  - Linux >= 5.10.173 < 5.11
  - Linux >= 5.15.100 < 5.16
  - Linux >= 6.2.5 < 6.3
  - Linux 6.3
ssvc:
  exploitation: none
  automatable: 'no'
  technicalImpact: partial
  timestamp: '2026-11-05T20:32:37.874530Z'
published: '2025-01-11'
updated: '2026-11-05'
sourceUpdated: '2026-11-05T20:41:37.859Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2024-57876'
references:
  - url: 'https://git.kernel.org/stable/c/94b33b2d7640e807869451384eb88321dd0ffbd4'
  - url: 'https://git.kernel.org/stable/c/d834d20d2e86c52ed5cab41763fa61e6071680ef'
  - url: 'https://git.kernel.org/stable/c/be826b4451fd187a7c0b04be4f8243d5df6e0450'
  - url: 'https://git.kernel.org/stable/c/a6fa67d26de385c3c7a23c1e109a0e23bfda4ec7'
tags:
  - cve.org
epss: 0.00163
epssPercentile: 0.05526
ingestedAt: '2026-11-05T22:38:31.845Z'
---

## Overview

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

- `Linux >= b30fcedeba643ca16eaa6212c1245598b7cd830d < 94b33b2d7640e807869451384eb88321dd0ffbd4`
- `Linux >= 1d082618bbf3b6755b8cc68c0a8122af2842d593 < d834d20d2e86c52ed5cab41763fa61e6071680ef`
- `Linux >= 1d082618bbf3b6755b8cc68c0a8122af2842d593 < be826b4451fd187a7c0b04be4f8243d5df6e0450`
- `Linux >= 1d082618bbf3b6755b8cc68c0a8122af2842d593 < a6fa67d26de385c3c7a23c1e109a0e23bfda4ec7`
- `Linux ee4a4282d78d96e07e714c28ca54679713fa2157`
- `Linux db35e49413a4d03ea0c003598803e49956f59324`
- `Linux a579ed4613b5a64074963988ad481e43cf3b917b`
- `Linux >= 6.1.18 < 6.1.120`
- `Linux >= 5.10.173 < 5.11`
- `Linux >= 5.15.100 < 5.16`
- `Linux >= 6.2.5 < 6.3`
- `Linux 6.3`

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.