CVE-2024-56616drm/dp_mst: Fix MST sideband message body length check
- 7.8HighCVSS base score
- 0.22%Exploitation in 30 daysEPSS · top 88% 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 MST sideband message body length check Fix the MST sideband message body length check, which must be at least 1 byte accounting for the message body CRC (aka message data CRC) at the end of the message. This fixes a case where an MST branch device returns a header with a correct header CRC (indicating a correctly received body length), with the body length being incorrectly set to 0. This will later lead to a memory corruption in drm_dp_sideband_append_payload() and the following errors in dmesg: UBSAN: array-index-out-of-bounds in drivers/gpu/drm/display/drm_dp_mst_topology.c:786:25 index -1 is out of range for type 'u8 [48]' Call Trace: drm_dp_sideband_append_payload+0x33d/0x350 [drm_display_helper] drm_dp_get_one_sb_msg+0x3ce/0x5f0 [drm_display_helper] drm_dp_mst_hpd_irq_handle_event+0xc8/0x1580 [drm_display_helper] memcpy: detected field-spanning write (size 18446744073709551615) of single field "&msg->msg[msg->curlen]" at drivers/gpu/drm/display/drm_dp_mst_topology.c:791 (size 256) Call Trace: drm_dp_sideband_append_payload+0x324/0x350 [drm_display_helper] drm_dp_get_one_sb_msg+0x3ce/0x5f0 [drm_display_helper] drm_dp_mst_hpd_irq_handle_event+0xc8/0x1580 [drm_display_helper]
Timeline
ID reserved
By Linux
Published
- 17 months later
· 17 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.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.22% · top 88% of all CVEs (19 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected ad7f8a1f9ced7f049f9b66d588723f243a7034cd – < 109f91d8b9335b0f3714ef9920eae5a8b21d56af
- affected ad7f8a1f9ced7f049f9b66d588723f243a7034cd – < 70e7166612f4e6da8d7d0305c47c465d88d037e5
- affected ad7f8a1f9ced7f049f9b66d588723f243a7034cd – < 780fa184d4dc38ad6c4fded345ab8f9be7a63e96
- affected ad7f8a1f9ced7f049f9b66d588723f243a7034cd – < c58947a8d4a500902597ee1dbadf0518d7ff8801
- affected ad7f8a1f9ced7f049f9b66d588723f243a7034cd – < 1fc1f32c4a3421b9d803f18ec3ef49db2fb5d5ef
- affected ad7f8a1f9ced7f049f9b66d588723f243a7034cd – < bd2fccac61b40eaf08d9546acc9fef958bfe4763
- affected 3.17
- unaffected < 3.17
- unaffected 5.10.233 – ≤ 5.10.*
- unaffected 5.15.176 – ≤ 5.15.*
- unaffected 6.1.120 – ≤ 6.1.*
- unaffected 6.6.66 – ≤ 6.6.*
- unaffected 6.12.5 – ≤ 6.12.*
- unaffected 6.13 – ≤ *
References
References8
- https://git.kernel.org/stable/c/109f91d8b9335b0f3714ef9920eae5a8b21d56af (opens in a new tab)
- https://git.kernel.org/stable/c/70e7166612f4e6da8d7d0305c47c465d88d037e5 (opens in a new tab)
- https://git.kernel.org/stable/c/780fa184d4dc38ad6c4fded345ab8f9be7a63e96 (opens in a new tab)
- https://git.kernel.org/stable/c/c58947a8d4a500902597ee1dbadf0518d7ff8801 (opens in a new tab)
- https://git.kernel.org/stable/c/1fc1f32c4a3421b9d803f18ec3ef49db2fb5d5ef (opens in a new tab)
- https://git.kernel.org/stable/c/bd2fccac61b40eaf08d9546acc9fef958bfe4763 (opens in a new tab)
- https://lists.debian.org/debian-lts-announce/2025/03/msg00001.html (opens in a new tab)
- https://lists.debian.org/debian-lts-announce/2025/03/msg00002.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-53264 (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-56616)Record last updated .