CVE-2026-112272 in libdisplay-info
Summary
by MITRE • 10/19/2026
Libdisplay-info 0.4.0 contains a heap out-of-bounds read vulnerability in the DisplayID v2 section parser in displayid2.c that allows attackers to read past the EDID buffer via oversized data block lengths. Attackers can supply a crafted EDID from a malicious monitor, KVM, capture device, or file to over-advance the parse cursor and crash applications.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Analysis
by VulDB Data Team • 10/19/2026
The vulnerability identified in Libdisplay-info version 0.4.0 represents a critical heap-based out-of-bounds read flaw located within the DisplayID v2 section parser implementation found in displayid2.c. This security issue stems from an insufficient validation of data block lengths during the parsing process for EDID Extended Display Identification Data structures. When the library processes input containing oversized data block length fields, it fails to properly bound-check the access against the allocated heap memory buffer. Consequently, the parse cursor is advanced beyond the valid boundaries of the assigned memory region, leading to a read operation that accesses unauthorized or uninitialized memory locations outside the intended buffer limits.
From an operational perspective, this vulnerability allows attackers with the ability to supply crafted EDID data to exploit the flaw in multiple scenarios. Malicious actors can utilize compromised monitors, KVM switches, video capture devices, or even local files containing specially constructed EDID blocks to trigger the out-of-bounds read condition. The immediate consequence of exploiting this weakness is often a denial of service manifested as an application crash due to segmentation faults or memory access violations triggered by reading invalid heap addresses. However, depending on the specific architecture and compiler optimizations employed in the consuming application, such reads may also lead to information disclosure if the accessed out-of-bounds memory contains sensitive data that can be exfiltrated through subsequent logic flows or error handling mechanisms within the host software.
This vulnerability is technically classified under CWE-125, which denotes Out-of-Bounds Read, as it involves accessing memory beyond the allocated buffer boundaries without proper bounds checking. In terms of attack vectors and techniques, this flaw aligns with MITRE ATT&CK technique T1083, specifically related to File and Directory Discovery or potentially data exfiltration if information leakage occurs, although its primary manifestation is often stability disruption via crash conditions in display management services like GNOME Shell or Wayland compositors that rely on Libdisplay-info for hardware identification. The exploitation requires the attacker to have some level of interaction with the system's input pipeline, such as physically connecting a malicious device or tricking a user into opening a crafted file within an application that utilizes this library for display configuration analysis.
Mitigation strategies primarily involve updating Libdisplay-info to patched versions where developers have implemented strict validation checks on data block lengths before proceeding with parsing operations. Developers integrating this library should ensure they are using the latest stable release which addresses these boundary conditions. Additionally, defense-in-depth measures such as enabling Address Sanitizer during development and testing phases can help detect similar memory safety issues early in the software lifecycle. For end-users, restricting physical access to display ports or ensuring that only trusted hardware is connected to critical systems reduces the attack surface for this specific vector of exploitation involving malicious EDID data injection.