Kernel memory corruption via zero-length MST message
Published Dec 27, 2024 · Updated May 11, 2026
Memory corruption in Linux DRM DisplayPort MST code allows physically proximate attackers to corrupt kernel memory via a branch device. drm_dp_decode_sideband_msg_hdr accepts a zero message length even though the trailing body CRC requires at least one byte, so drm_dp_sideband_append_payload indexes before the buffer and passes an underflowed length to memcpy. A crafted or faulty DisplayPort MST branch device is required; published evidence demonstrates kernel-memory corruption but does not establish a specific follow-on outcome.
Summary
What happened
Memory corruption in Linux DRM DisplayPort MST code allows physically proximate attackers to corrupt kernel memory via a branch device. drm_dp_decode_sideband_msg_hdr accepts a zero message length even though the trailing body CRC requires at least one byte, so drm_dp_sideband_append_payload indexes before the buffer and passes an underflowed length to memcpy. A crafted or faulty DisplayPort MST branch device is required; published evidence demonstrates kernel-memory corruption but does not establish a specific follow-on outcome.
The record
- CVE
- CVE-2024-56616
- Published
- Dec 27, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1200
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 27, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.17
- Affected versionversion=ad7f8a1f9ced7f049f9b66d588723f243a7034cd <109f91d8b9335b0f3714ef9920eae5a8b21d56af
- Affected versionversion=ad7f8a1f9ced7f049f9b66d588723f243a7034cd <1fc1f32c4a3421b9d803f18ec3ef49db2fb5d5ef
- Affected versionversion=ad7f8a1f9ced7f049f9b66d588723f243a7034cd <70e7166612f4e6da8d7d0305c47c465d88d037e5
- Affected versionversion=ad7f8a1f9ced7f049f9b66d588723f243a7034cd <780fa184d4dc38ad6c4fded345ab8f9be7a63e96
- Affected versionversion=ad7f8a1f9ced7f049f9b66d588723f243a7034cd <bd2fccac61b40eaf08d9546acc9fef958bfe4763
- Affected versionversion=ad7f8a1f9ced7f049f9b66d588723f243a7034cd <c58947a8d4a500902597ee1dbadf0518d7ff8801
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo