CVE-2026-98202
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.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
Propose a mitigation on Community Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
References
- https://git.kernel.org/stable/c/30366f507ce3e408caf7f7375bb343df54b9a4f9
- https://git.kernel.org/stable/c/7a3d7c68aa36f68e2a4824da4782c0e5d7c4eba4
- https://git.kernel.org/stable/c/84145a4a1dc58f8959811913c5f61f3235dd9f6c
- https://git.kernel.org/stable/c/942b06a19252908d0f952c0590caf20e47f88252
- https://git.kernel.org/stable/c/e2b6703465c1ce43edb91c1626604b7092b3c431
- https://git.kernel.org/stable/c/fa1713dc3d43d028d6cb66e5659d9d7e83b73362
- https://git.kernel.org/stable/c/fafca210631d8c2d4311bdfccc5ec46b9fe65977
- https://git.kernel.org/stable/c/fe10579b6dc3f0dac61e51e1797cacbba5039ac2
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.