CVE-2026-99628: drm/amd/display: Avoid closing unowned DDC pins
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Avoid closing unowned DDC pins
[WHY] dalddcopen() 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, dalddcopen() closes the pins it opened. An extra dalddcclose() is unnecessary and unsafe: GPIORESULTALREADYOPENED can mean AUX owns the existing handles, and closing them here would disrupt AUX.
[HOW] Remove the extra dalddcclose() from the failed-open path.
(cherry picked from commit 175ae7772b68757b4932f34ff862923cab7abe21)
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.118 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.64 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.5 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Patch 175ae7772b68757b4932f34ff862923cab7abe21
Frequently Asked Questions
Which systems are most likely to be exposed to this issue?
Systems using the Linux kernel AMD display driver are relevant, particularly where DDC pin opening can fail while AUX already owns existing GPIO handles. The failure can disrupt AUX by closing handles that were not acquired by the failing DDC operation.
What condition triggers the unsafe behavior?
The issue occurs on the failed-open path in dal_ddc_open() when an extra dal_ddc_close() is called after pin acquisition or configuration fails. GPIO_RESULT_ALREADY_OPENED can indicate that AUX owns the existing handles, so the extra close can release unowned pins.
How is the issue fixed?
The fix removes the extra dal_ddc_close() call from the failed-open path. dal_ddc_open() already cleans up pins it successfully acquired when later operations fail.