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

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

[Greg Kroah-Hartman]

From: Greg Kroah-Hartman <gregkh@kernel.org>

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.

The Linux kernel CVE team has assigned CVE-2026-98202 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 4.6 with commit 2b6a321da9a2d8725a1d3dbb0b2e96a7618ebe56 and fixed in 5.10.271 with commit 7a3d7c68aa36f68e2a4824da4782c0e5d7c4eba4
	Issue introduced in 4.6 with commit 2b6a321da9a2d8725a1d3dbb0b2e96a7618ebe56 and fixed in 5.15.222 with commit fafca210631d8c2d4311bdfccc5ec46b9fe65977
	Issue introduced in 4.6 with commit 2b6a321da9a2d8725a1d3dbb0b2e96a7618ebe56 and fixed in 6.1.189 with commit 84145a4a1dc58f8959811913c5f61f3235dd9f6c
	Issue introduced in 4.6 with commit 2b6a321da9a2d8725a1d3dbb0b2e96a7618ebe56 and fixed in 6.6.158 with commit e2b6703465c1ce43edb91c1626604b7092b3c431
	Issue introduced in 4.6 with commit 2b6a321da9a2d8725a1d3dbb0b2e96a7618ebe56 and fixed in 6.12.112 with commit 30366f507ce3e408caf7f7375bb343df54b9a4f9
	Issue introduced in 4.6 with commit 2b6a321da9a2d8725a1d3dbb0b2e96a7618ebe56 and fixed in 6.18.54 with commit fa1713dc3d43d028d6cb66e5659d9d7e83b73362
	Issue introduced in 4.6 with commit 2b6a321da9a2d8725a1d3dbb0b2e96a7618ebe56 and fixed in 7.2.8 with commit 942b06a19252908d0f952c0590caf20e47f88252
	Issue introduced in 4.6 with commit 2b6a321da9a2d8725a1d3dbb0b2e96a7618ebe56 and fixed in 7.3-rc4 with commit fe10579b6dc3f0dac61e51e1797cacbba5039ac2

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2026-98202
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	drivers/input/rmi4/rmi_driver.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	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