Input: synaptics-rmi4 - fix GPF in suspend and resume when unbound
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux 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 Linux
4.6
- KernelLinux
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
References 8
git.kernel.org
- stable/c/7a3d7c68aa36f68e2a4824da4782c0e5d7c4eba4
- stable/c/fafca210631d8c2d4311bdfccc5ec46b9fe65977
- stable/c/84145a4a1dc58f8959811913c5f61f3235dd9f6c
- stable/c/e2b6703465c1ce43edb91c1626604b7092b3c431
- stable/c/30366f507ce3e408caf7f7375bb343df54b9a4f9
- stable/c/fa1713dc3d43d028d6cb66e5659d9d7e83b73362
- stable/c/942b06a19252908d0f952c0590caf20e47f88252
- stable/c/fe10579b6dc3f0dac61e51e1797cacbba5039ac2