Skip to main content
Vulnerability Database/CVE-2024-57887

CVE-2024-57887: Linux Kernel Use-After-Free Vulnerability

CVE-2024-57887 is a use-after-free vulnerability in the Linux Kernel DRM ADV7511 driver that could lead to memory corruption. This article covers the technical details, affected kernel versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2024-57887 Overview

CVE-2024-57887 is a use-after-free vulnerability [CWE-416] in the Linux kernel's Analog Devices ADV7511/ADV7533 Direct Rendering Manager (DRM) bridge driver. The flaw resides in the adv7533_attach_dsi() function, which dereferences a host_node device-tree pointer that was already released by adv7533_parse_dt(). A local attacker with low privileges can trigger memory corruption through the vulnerable driver path, leading to kernel instability or code execution in kernel context.

Critical Impact

Local attackers can exploit this use-after-free in the ADV7511 DRM bridge driver to corrupt kernel memory, potentially achieving privilege escalation or denial of service on affected Linux systems.

Affected Products

  • Linux kernel stable branches containing the ADV7511 DRM bridge driver prior to the fix
  • Linux kernel 6.13 release candidates (rc1 through rc5)
  • Debian LTS distributions shipping the vulnerable kernel package

Discovery Timeline

  • 2025-01-15 - CVE-2024-57887 published to the National Vulnerability Database
  • 2026-06-17 - Last updated in NVD database

Technical Details for CVE-2024-57887

Vulnerability Analysis

The vulnerability exists in drivers/gpu/drm/bridge/adv7511/adv7533.c, part of the ADV7511 HDMI transmitter bridge driver. During device probe, adv7533_parse_dt() retrieves the DSI host device-tree node via of_graph_get_remote_node() and assigns the result to adv->host_node. The function then immediately calls of_node_put() on that pointer, decrementing its reference count before the driver finishes using it.

Later, adv7533_attach_dsi() dereferences adv->host_node to look up and attach the MIPI DSI host. By this point the node may have been freed, producing a classic use-after-free condition in kernel memory. Memory allocator reuse of the freed slab object can allow an attacker to influence subsequent dereferences.

Root Cause

The root cause is incorrect reference-count management on an of_node structure. adv7533_parse_dt() releases the node reference it stores, violating the ownership contract expected by adv7533_attach_dsi() and the remove() path. The upstream fix removes the premature of_node_put() from adv7533_parse_dt() and relocates the release to the probe error path and the driver's remove() function so the node lifetime matches its usage.

Attack Vector

Exploitation requires local access and the ability to interact with the DRM subsystem on a system that instantiates the ADV7511/ADV7533 bridge. Triggering the vulnerable code path involves driver (re)binding or probe sequences that execute adv7533_attach_dsi() after the device-tree node has been released. Successful exploitation can corrupt kernel heap objects allocated into the freed slab, impacting confidentiality, integrity, and availability.

No public proof-of-concept exploit is available, and the issue is not listed on the CISA Known Exploited Vulnerabilities catalog.

Detection Methods for CVE-2024-57887

Indicators of Compromise

  • Kernel oops or BUG: KASAN: use-after-free messages in dmesg referencing adv7533_attach_dsi or adv7511_bridge symbols
  • Unexpected crashes or soft lockups during DRM bridge probe on hardware using the ADV7511/ADV7533 chip
  • Repeated bind/unbind events against the ADV7511 driver recorded in system logs

Detection Strategies

  • Enable KASAN (Kernel Address Sanitizer) on test and staging kernels to catch use-after-free dereferences during driver probe
  • Audit running kernel versions against the fixed stable commits 1f49aaf5, 81adbd3f, ca9d0773, and d2085719
  • Monitor for abnormal userspace processes writing to /sys/bus/platform/drivers/adv7511/bind or unbind

Monitoring Recommendations

  • Centralize kernel ring-buffer logs to a SIEM and alert on KASAN, general protection fault, and slab-use-after-free strings
  • Track package versions of linux-image-* across Debian LTS fleets and flag hosts not aligned with the latest security update
  • Baseline DRM driver load events on embedded devices and alert on anomalous rebind activity

How to Mitigate CVE-2024-57887

Immediate Actions Required

  • Apply vendor-supplied kernel updates on all Linux systems that build or load the ADV7511 DRM bridge driver
  • Prioritize patching embedded platforms and single-board computers that use ADV7511/ADV7533 HDMI output hardware
  • Restrict local shell and driver-binding access to trusted administrators until systems are patched

Patch Information

The upstream fix removes the premature of_node_put() from adv7533_parse_dt() and adds matching of_node_put() calls in the probe error path and the remove() handler. Fix commits are available in the stable tree: 1f49aaf5, 81adbd3f, ca9d0773, and d2085719. Debian users should consult the Debian LTS Announcement (March 2025 #1) and Debian LTS Announcement (March 2025 #2).

Workarounds

  • Disable or blacklist the adv7511 kernel module on systems that do not require the ADV7511/ADV7533 bridge
  • Remove unprivileged access to driver bind/unbind sysfs entries by tightening permissions on /sys/bus/platform/drivers/adv7511/
  • Enforce kernel lockdown mode where supported to reduce the local attack surface against DRM subsystems

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.