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

> A local attacker can cause a system crash via a NULL pointer dereference in the Synaptics RMI4 driver during suspend or resume if the device is unbound.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-106449, BELL-CVE-2026-98202, DEBIAN-CVE-2026-98202, GHSA-4pg4-5mfg-2p8v, UBUNTU-CVE-2026-98202

## What is CVE-2026-98202?

CVE-2026-98202 is a vulnerability in Linux, published on 6 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

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

## Which versions are affected by CVE-2026-98202?


## How do I fix CVE-2026-98202?

Apply the vendor's patch.

## Is CVE-2026-98202 being exploited?

There is no known exploitation of CVE-2026-98202 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-98202 and fix it if it is affected.

What it is: CVE-2026-98202 is a vulnerability in Linux, published on 6 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-98202 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-98202/ (Markdown: https://insights.sbomify.com/CVE-2026-98202/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-98202
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-98202
- OSV: https://osv.dev/vulnerability/CVE-2026-98202

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-98202/
Summaries are generated and may contain mistakes; the official description above is the record.