CVE intelligence

CVE-2024-56616

Vulnerability intelligence

Published Dec 27, 2024Sources checked Nov 10, 2026

7.8HIGHCVSS out of 10

What this means

Review the available evidence

CVE-2024-56616 and is rated High severity with a CVSS score of 7.8. It is not in the current CISA KEV record we collected. That does not prove exploitation has not occurred.

What to do next

Remediation and response

Ubuntu Security Notices guidance

Vendor revision: Nov 10, 2026

Vendor remediation details

This update corrects flaws in the following subsystems: - GPU drivers; - IIO ADC drivers; - Multiple devices driver; - Ethernet bonding driver; - Network drivers; - PCI subsystem; - VFIO drivers; - File systems infrastructure; - F2FS file system; - JFS file system; - Network file system (NFS) server daemon; - OCFS2 file system; - Overlay file system; - Tracing infrastructure; - IUCV driver; (CVE-2021-47633, CVE-2022-49058, CVE-2022-49170, CVE-2023-52784, CVE-2024-53194, CVE-2024-53210, CVE-2024-53214, CVE-2024-56570, CVE-2024-56616, CVE-2024-56763, CVE-2024-56779, CVE-2024-57904, CVE-2025-21664, CVE-2025-38604, CVE-2025-39743, CVE-2026-43456, CVE-2026-74350)

Ubuntu Security Notices guidance

Vendor revision: Nov 10, 2026

Vendor remediation details

This update corrects flaws in the following subsystems: - GPU drivers; - Ethernet bonding driver; - Network drivers; - F2FS file system; - Tracing infrastructure; - Networking core; - IUCV driver; - RxRPC session sockets; (CVE-2022-49149, CVE-2022-49170, CVE-2023-52784, CVE-2024-53210, CVE-2024-56616, CVE-2024-56763, CVE-2026-43456, CVE-2026-52910, CVE-2026-53086)

Ubuntu Security Notices guidance

Vendor revision: Nov 10, 2026

Vendor remediation details

CISA KEVNot listedBased on the latest collected catalog

EPSS0.2%Estimated 30-day exploitation probability

Ransomware useNot markedCISA KEV ransomware field

Threat actors0Source-linked actor relationships

Overview

What is CVE-2024-56616?

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]

Source: NVD