Input: synaptics-rmi4 - fix GPF in suspend and resume when unbound
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 2b6a321da9a2d8725a1d3dbb0b2e96a7618ebe56 · < fa1713dc3d43d028d6cb66e5659d9d7e83b73362| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s synaptics-rmi4 driver can hit a NULL pointer dereference and General Protection Fault during suspend or resume if the RMI device is unbound. The input does not describe an attacker path, authentication requirement, or user interaction.
Engineers running Linux kernels with synaptics-rmi4 should check whether their kernel is affected; affected versions are not specified.