Live › vulnerability › CVE-2026-98605
Go to dashboardThe Samsung DSI display bridge driver in the Linux kernel mixed a managed GPIO acquisition with explicit releases, so repeated host attach and detach could request a GPIO that was not released. The sources do not describe an attacker outcome.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Systems running a Linux kernel with the samsung-dsim DRM bridge driver, typically Exynos-based ARM boards with a DSI display. Servers and desktops without that hardware driver are unlikely to be affected. The sources do not state the fixed kernel version.
No product ranges from the sources yet.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
In the Linux kernel, the following vulnerability has been resolved:
drm/bridge: samsung-dsim: fix TE GPIO lifetime for host attach
When the Exynos DSI driver was generalized into samsung-dsim, the TE GPIO acquisition was switched from gpiod_get_optional() to devm_gpiod_get_optional() while keeping the matching gpiod_put() calls. That combination is wrong for a managed descriptor.
However, dropping the puts and keeping the managed get is also wrong: samsung_dsim_register_te_irq() runs from the DSI host attach callback, and host detach/reattach can happen without destroying the device that owns the managed action. A second attach would then request the GPIO again without having released it.
Switch back to a non-managed gpiod_get_optional() and keep the explicit gpiod_put() on the request_irq() error path and in samsung_dsim_unregister_te_irq().
[Luca: remove unnecessary comment]
This page as .md · .json · in your agent: get_signal("CVE-2026-98605")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.