https://db.gcve.eu/rss/recent/all/10 Most recent entries from all 2026-10-17T17:23:36.312733+00:00 Vulnerability-Lookup info@gcve.eu python-feedgen Contains only the most 10 recent entries. https://db.gcve.eu/vuln/fkie_cve-2026-98202 fkie_cve-2026-98202 2026-10-17T17:23:36.342372+00:00

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.

 https://db.gcve.eu/vuln/ghsa-4pg4-5mfg-2p8v GHSA-4pg4-5mfg-2p8v 2026-10-17T17:23:36.342452+00:00

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.

 https://db.gcve.eu/vuln/msrc_cve-2026-98202 msrc_CVE-2026-98202 — Input: synaptics-rmi4 - fix GPF in suspend and resume when unbound 2026-10-17T17:23:36.342480+00:00 msrc_CVE-2026-98202 https://db.gcve.eu/vuln/opensuse-su-2026:12131-1 openSUSE-SU-2026:12131-1 — kernel-devel-7.2.10-1.1 on GA media 2026-10-17T17:23:36.342501+00:00

kernel-devel-7.2.10-1.1 on GA media

 https://db.gcve.eu/vuln/ubuntu-cve-2026-98202 UBUNTU-CVE-2026-98202 2026-10-17T17:23:36.342618+00:00

Affected: Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 240 more

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.