Kernel crash via unbound RMI suspend callbacks
Published Oct 6, 2026 · Updated Oct 6, 2026
A NULL-pointer dereference in the Linux synaptics-rmi4 driver allows context-dependent attackers to crash the kernel during device suspend or resume. The rmi_driver_suspend() and rmi_driver_resume() callbacks proceed without driver data when an RMI device has not bound, then dereference that missing data in power-management work. A demonstrated trigger uses privileged USB emulation and runtime power management; a network-only trigger has not been shown.
Summary
What happened
A NULL-pointer dereference in the Linux synaptics-rmi4 driver allows context-dependent attackers to crash the kernel during device suspend or resume. The rmi_driver_suspend() and rmi_driver_resume() callbacks proceed without driver data when an RMI device has not bound, then dereference that missing data in power-management work. A demonstrated trigger uses privileged USB emulation and runtime power management; a network-only trigger has not been shown.
The record
- CVE
- CVE-2026-98202
- Published
- Oct 6, 2026
- Updated
- Oct 6, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Oct 6, 2026CVE publishedPublication date reported by the CVE source.
- Oct 6, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2b6a321da9a2d8725a1d3dbb0b2e96a7618ebe56 <30366f507ce3e408caf7f7375bb343df54b9a4f9
- Affected versionversion=2b6a321da9a2d8725a1d3dbb0b2e96a7618ebe56 <7a3d7c68aa36f68e2a4824da4782c0e5d7c4eba4
- Affected versionversion=2b6a321da9a2d8725a1d3dbb0b2e96a7618ebe56 <84145a4a1dc58f8959811913c5f61f3235dd9f6c
- Affected versionversion=2b6a321da9a2d8725a1d3dbb0b2e96a7618ebe56 <942b06a19252908d0f952c0590caf20e47f88252
- Affected versionversion=2b6a321da9a2d8725a1d3dbb0b2e96a7618ebe56 <e2b6703465c1ce43edb91c1626604b7092b3c431
- Affected versionversion=2b6a321da9a2d8725a1d3dbb0b2e96a7618ebe56 <fa1713dc3d43d028d6cb66e5659d9d7e83b73362
- Affected versionversion=2b6a321da9a2d8725a1d3dbb0b2e96a7618ebe56 <fafca210631d8c2d4311bdfccc5ec46b9fe65977
- Affected versionversion=2b6a321da9a2d8725a1d3dbb0b2e96a7618ebe56 <fe10579b6dc3f0dac61e51e1797cacbba5039ac2
- Affected versionversion=4.6
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
- syzbot USB-emulation crash reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started