CVE-2026-99628 in Linuxinfo

Summary

by MITRE • 11/20/2026

In the Linux kernel, the following vulnerability has been resolved:

drm/amd/display: Avoid closing unowned DDC pins

[WHY]
dal_ddc_open() cleans up pins it acquires on later failures. If the data-pin open fails, this attempt acquired nothing. If opening the clock pin or configuring fails, dal_ddc_open() closes the pins it opened. An extra dal_ddc_close() is unnecessary and unsafe: GPIO_RESULT_ALREADY_OPENED can mean AUX owns the existing handles, and closing them here would disrupt AUX.

[HOW]
Remove the extra dal_ddc_close() from the failed-open path.

(cherry picked from commit 175ae7772b68757b4932f34ff862923cab7abe21)

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Analysis

by VulDB Data Team • 11/21/2026

The vulnerability identified in the Linux kernel's Direct Rendering Manager subsystem, specifically within the AMD display driver component known as Display Core or DAL, involves an improper resource management sequence during Dynamic Data Channel initialization. This issue centers on the handling of General Purpose Input/Output pins designated for DDC communication, which is critical for monitor detection and configuration via I2C protocols. The root cause lies in a logic error within the dal_ddc_open function where cleanup routines are executed even when they should not be, leading to potential race conditions or state corruption involving hardware resources that are managed by other subsystems.

The technical flaw manifests during the initialization phase of DDC pins for display outputs. When the driver attempts to open these pins, it may encounter failures at various stages, such as acquiring a data pin versus a clock pin, or failing configuration steps after partial acquisition. The original code logic indiscriminately called dal_ddc_close on any failure path within this sequence. However, if an earlier step in the process had already successfully acquired handles for certain pins, and subsequent steps failed, closing those previously opened pins was incorrect. More critically, if a pin is reported as ALREADY_OPENED by the GPIO subsystem, it indicates that another driver component, typically the AUX channel handler responsible for DisplayPort auxiliary communications, currently owns or shares control over that hardware resource. Forcing a close operation in this context disrupts the state of the owning entity, potentially causing undefined behavior, system instability, or display output failures.

From an operational perspective, this vulnerability can lead to significant reliability issues in systems utilizing AMD graphics hardware with DisplayPort outputs. The immediate impact includes potential crashes within the kernel space when the driver attempts to access resources that have been improperly released while still in use by another context. This can result in a system hang or require a reboot to restore proper display functionality. Furthermore, it may cause intermittent failures where monitor detection fails because the DDC bus is left in an inconsistent state, preventing the operating system from correctly identifying connected displays and their capabilities such as resolution and refresh rate support.

This issue aligns with CWE-401, which describes a missing release of memory or other resources after allocation, although here it specifically involves improper resource deallocation rather than simple leakage. The behavior also touches upon CWE-362 regarding concurrent execution race conditions if the premature closure interferes with ongoing operations by the AUX channel handler. In terms of MITRE ATT&CK mapping, while this is primarily a stability and reliability bug rather than an exploitable security vulnerability for privilege escalation or remote code execution in most contexts, it relates to T1499 Endpoint Denial of Service if triggered repeatedly under specific load conditions that cause kernel panics or display subsystem failures.

To mitigate the risks associated with this flaw, system administrators should ensure that their Linux kernels are updated to include the patch corresponding to commit 175ae7772b68757b4932f34ff862923cab7abe2 or later versions of the stable kernel series. For users compiling custom kernels, this change must be applied within the drm/amd/display/dal/services/ddc directory to correct the conditional logic surrounding dal_ddc_close calls. It is essential to verify that the GPIO subsystem correctly reports ownership status before any cleanup operations are attempted in display driver initialization paths. Maintaining up-to-date kernel versions ensures that these resource management safeguards remain intact, preserving system stability and proper hardware interaction for AMD GPU users.

Responsible

Linux

Reservation

09/25/2026

Disclosure

11/20/2026

Moderation

accepted

CPE

ready

EPSS

0.00201

KEV

no

Activities

very low

Sources

Do you need the next level of professionalism?

Upgrade your account now!