CVE-2026-98605: drm/bridge: samsung-dsim: fix TE GPIO lifetime for host attach
drm/bridge: samsung-dsim: fix TE GPIO lifetime for host attach
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 6.6.159.1-1 - Upgrade
Upgrade
ubuntu/linux-hwe-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42~24.04.1 - Upgrade
Upgrade
ubuntu/linux-riscv-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1~24.04.1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 7.0.0-42.42 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 7.0.0-1016.17 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 7.0.0-1016.18 - Upgrade
Upgrade
ubuntu/linux-ibmto a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oem-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 7.0.0-1015.16 - Upgrade
Upgrade
ubuntu/linux-riscvto a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.6.158 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.112 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.55 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.2.9
Event History
Frequently Asked Questions
Which systems are exposed to this issue?
Systems using the Linux kernel samsung-dsim DRM bridge driver with a TE GPIO configured are affected. The problem is tied to DSI host attach, detach, and reattach handling rather than to all Linux kernel systems generally.
What condition triggers the faulty GPIO lifetime handling?
The condition can occur when the DSI host is detached and later reattached without destroying the device that owns the managed GPIO action. On the second attach, the driver can attempt to request the TE GPIO again even though the prior managed acquisition was not released.
Is a default configuration necessarily affected?
No. The affected path concerns the optional TE GPIO used by the samsung-dsim driver, so systems without that GPIO configured do not use this acquisition path.
What is the relevant remediation?
Use the corrected driver behavior that acquires the TE GPIO with non-managed gpiod_get_optional() and explicitly releases it on IRQ-request failure and during TE IRQ unregistration. This ensures the GPIO is released between host detach and reattach operations.