Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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]

Timeline

  1. ID reserved

    By Linux

  2. · 23 days later

    Published

  3. · 1 day later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 94% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected e7447128ca4a250374d6721ee98e3e3cf99551a6 – < 77a43e00c57486a5212ef22d4665cafad62a5d4b
    • affected e7447128ca4a250374d6721ee98e3e3cf99551a6 – < 5759bbef951c39d264ac0f47daa4137d01403aea
    • affected e7447128ca4a250374d6721ee98e3e3cf99551a6 – < ebffd70e4877bb7554974cf975a27872f2bb225f
    • affected e7447128ca4a250374d6721ee98e3e3cf99551a6 – < 9b796251c3cca45a33a5c859c6818c58aa982277
    • affected e7447128ca4a250374d6721ee98e3e3cf99551a6 – < ada667890773e033d2f40dc94176e3beb930b516
  • Linux · Linux

    • affected 6.4
    • unaffected < 6.4
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.112 – ≤ 6.12.*
    • unaffected 6.18.55 – ≤ 6.18.*
    • unaffected 7.2.9 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-98605 badge
[![CVE-2026-98605](https://cveledger.app/badge/CVE-2026-98605.svg)](https://cveledger.app/cve/CVE-2026-98605)

Record last updated .