CVE-2026-98202: Linux kernel · Input: synaptics-rmi4 – fix GPF in suspend and resume when unbound
Affects Linux kernelSource GCVE Database
Not known to be exploited.
Data as of 28 Oct 2026, 01:27 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
Exploitation evidence
Disclosed: evidence found.
CVE published 6 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.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-azure-fdepkg:deb/ubuntu/linux-azure-fde?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-gkepkg:deb/ubuntu/linux-gke?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
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.
References
- ubuntu.com/security/CVE-2026-98202 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-98202 (opens in a new tab)
- git.kernel.org/linus/fe10579b6dc3f0dac61e51e1797cacbba5039ac2 (opens in a new tab)
- git.kernel.org/stable/c/30366f507ce3e408caf7f7375bb343df54b9a4f9 (opens in a new tab)
- git.kernel.org/stable/c/7a3d7c68aa36f68e2a4824da4782c0e5d7c4eba4 (opens in a new tab)
- git.kernel.org/stable/c/84145a4a1dc58f8959811913c5f61f3235dd9f6c (opens in a new tab)
- git.kernel.org/stable/c/942b06a19252908d0f952c0590caf20e47f88252 (opens in a new tab)
- git.kernel.org/stable/c/e2b6703465c1ce43edb91c1626604b7092b3c431 (opens in a new tab)
- git.kernel.org/stable/c/fa1713dc3d43d028d6cb66e5659d9d7e83b73362 (opens in a new tab)
- git.kernel.org/stable/c/fafca210631d8c2d4311bdfccc5ec46b9fe65977 (opens in a new tab)
- git.kernel.org/stable/c/fe10579b6dc3f0dac61e51e1797cacbba5039ac2 (opens in a new tab)