CVE-2026-98202Input: synaptics-rmi4 - fix GPF in suspend and resume when unbound
- —Not scoredno CVSS score yet
- 0.18%Exploitation in 30 daysEPSS · top 93% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: Input: synaptics-rmi4 - fix GPF in suspend and resume when unbound Transport drivers (such as rmi_i2c and rmi_spi) invoke rmi_driver_suspend() and rmi_driver_resume() on their child rmi_dev device during system power management events. However, transport drivers are fully registered and operational even if the physical RMI driver failed to bind or probe the rmi_dev device. When rmi_driver_suspend() or rmi_driver_resume() is called on an unbound rmi_dev, dev_get_drvdata() returns NULL. Calling rmi_disable_irq() or rmi_enable_irq() without driver data attached causes a NULL pointer dereference and General Protection Fault when attempting to lock data->enabled_mutex. Fix this by checking if driver data is attached to rmi_dev in rmi_driver_suspend() and rmi_driver_resume(), exiting early if no driver data is present.
Timeline
ID reserved
By Linux
- 11 days later
· 11 days later
Published
- 13 days later
· 13 days 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.18% · top 93% of all CVEs (15 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 2b6a321da9a2d8725a1d3dbb0b2e96a7618ebe56 – < 7a3d7c68aa36f68e2a4824da4782c0e5d7c4eba4
- affected 2b6a321da9a2d8725a1d3dbb0b2e96a7618ebe56 – < fafca210631d8c2d4311bdfccc5ec46b9fe65977
- affected 2b6a321da9a2d8725a1d3dbb0b2e96a7618ebe56 – < 84145a4a1dc58f8959811913c5f61f3235dd9f6c
- affected 2b6a321da9a2d8725a1d3dbb0b2e96a7618ebe56 – < e2b6703465c1ce43edb91c1626604b7092b3c431
- affected 2b6a321da9a2d8725a1d3dbb0b2e96a7618ebe56 – < 30366f507ce3e408caf7f7375bb343df54b9a4f9
- affected 2b6a321da9a2d8725a1d3dbb0b2e96a7618ebe56 – < fa1713dc3d43d028d6cb66e5659d9d7e83b73362
- affected 2b6a321da9a2d8725a1d3dbb0b2e96a7618ebe56 – < 942b06a19252908d0f952c0590caf20e47f88252
- affected 2b6a321da9a2d8725a1d3dbb0b2e96a7618ebe56 – < fe10579b6dc3f0dac61e51e1797cacbba5039ac2
- affected 4.6
- unaffected < 4.6
- unaffected 5.10.271 – ≤ 5.10.*
- unaffected 5.15.222 – ≤ 5.15.*
- unaffected 6.1.189 – ≤ 6.1.*
- unaffected 6.6.158 – ≤ 6.6.*
- unaffected 6.12.112 – ≤ 6.12.*
- unaffected 6.18.54 – ≤ 6.18.*
- unaffected 7.2.8 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References8
- https://git.kernel.org/stable/c/7a3d7c68aa36f68e2a4824da4782c0e5d7c4eba4 (opens in a new tab)
- https://git.kernel.org/stable/c/fafca210631d8c2d4311bdfccc5ec46b9fe65977 (opens in a new tab)
- https://git.kernel.org/stable/c/84145a4a1dc58f8959811913c5f61f3235dd9f6c (opens in a new tab)
- https://git.kernel.org/stable/c/e2b6703465c1ce43edb91c1626604b7092b3c431 (opens in a new tab)
- https://git.kernel.org/stable/c/30366f507ce3e408caf7f7375bb343df54b9a4f9 (opens in a new tab)
- https://git.kernel.org/stable/c/fa1713dc3d43d028d6cb66e5659d9d7e83b73362 (opens in a new tab)
- https://git.kernel.org/stable/c/942b06a19252908d0f952c0590caf20e47f88252 (opens in a new tab)
- https://git.kernel.org/stable/c/fe10579b6dc3f0dac61e51e1797cacbba5039ac2 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-93130 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-98202)Record last updated .