CVE-2026-98605VulnerabilityPublished 20 Oct 2026Updated 28 Oct 2026

Microsoft · drm/bridge: samsung-dsim: fix TE GPIO lifetime for host attach

Affects MicrosoftSource GCVE Database

Authoritative record:CVE-2026-98605

Not known to be exploited · fixed in ebffd70e4877bb7554974cf975a27872f2bb225f : update Microsoft when convenient.

Data as of 28 Oct 2026, 08:43 UTC

Severity

Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Patch: Available – fixed in ebffd70e4877bb7554974cf975a27872f2bb225f, ada667890773e033d2f40dc94176e3beb930b516, 5759bbef951c39d264ac0f47daa4137d01403aea +2

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

microsoft-security-response-ce

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ e7447128ca4a250374d6721ee98e3e3cf99551a6, < ebffd70e4877bb7554974cf975a27872f2bb225f	Fixed in ebffd70e4877bb7554974cf975a27872f2bb225f
LinuxLinux	Affected ≥ e7447128ca4a250374d6721ee98e3e3cf99551a6, < ada667890773e033d2f40dc94176e3beb930b516	Fixed in ada667890773e033d2f40dc94176e3beb930b516
LinuxLinux	Affected ≥ e7447128ca4a250374d6721ee98e3e3cf99551a6, < 5759bbef951c39d264ac0f47daa4137d01403aea	Fixed in 5759bbef951c39d264ac0f47daa4137d01403aea
LinuxLinux	Affected ≥ e7447128ca4a250374d6721ee98e3e3cf99551a6, < 77a43e00c57486a5212ef22d4665cafad62a5d4b	Fixed in 77a43e00c57486a5212ef22d4665cafad62a5d4b
LinuxLinux	Affected ≥ e7447128ca4a250374d6721ee98e3e3cf99551a6, < 9b796251c3cca45a33a5c859c6818c58aa982277	Fixed in 9b796251c3cca45a33a5c859c6818c58aa982277
LinuxLinux	Affected =6.4	Fixed in–

Description

To determine the support lifecycle for your software, see the Microsoft Support Lifecycle: https://support.microsoft.com/lifecycle

References

Community reviews

Loading reviews…