CVE-2026-98202
Input: synaptics-rmi4 - fix GPF in suspend and resume when unbound
No known exploitation. EPSS puts it in the 7th percentile. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- LinuxAffected: ≥ 2b6a321da9a2d8725a1d3dbb0b2e96a7618ebe56, < 7a3d7c68aa36f68e2a4824da4782c0e5d7c4eba4Upgrade to: 7a3d7c68aa36f68e2a4824da4782c0e5d7c4eba4Affected: ≥ 2b6a321da9a2d8725a1d3dbb0b2e96a7618ebe56, < fafca210631d8c2d4311bdfccc5ec46b9fe65977Upgrade to: fafca210631d8c2d4311bdfccc5ec46b9fe65977Affected: ≥ 2b6a321da9a2d8725a1d3dbb0b2e96a7618ebe56, < 84145a4a1dc58f8959811913c5f61f3235dd9f6cUpgrade to: 84145a4a1dc58f8959811913c5f61f3235dd9f6cAffected: ≥ 2b6a321da9a2d8725a1d3dbb0b2e96a7618ebe56, < e2b6703465c1ce43edb91c1626604b7092b3c431Upgrade to: e2b6703465c1ce43edb91c1626604b7092b3c431 + 4 more branchesStated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
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.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.2% chance of exploitation activity in the next 30 days, which ranks it in the 7th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
2 events over 0 days, from the signal feeds we watch.
- Publishedrecord updated
Affected products
Sources
References in the record
- git.kernel.org/stable/c/30366f507ce3e408caf7f7375bb343df54b9a4f9
- git.kernel.org/stable/c/7a3d7c68aa36f68e2a4824da4782c0e5d7c4eba4
- git.kernel.org/stable/c/84145a4a1dc58f8959811913c5f61f3235dd9f6c
And 5 more references. See all after sign-in
In the news
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Linux, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI