Linux Kernel up to 7.3-rc3 synaptics-rmi4 rmi_driver_suspend/rmi_driver_resume null pointer dereference

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, was found in Linux Kernel up to 7.3-rc3. This vulnerability affects the function rmi_driver_suspend/rmi_driver_resume of the component synaptics-rmi4. Such manipulation leads to null pointer dereference.
This vulnerability is traded as CVE-2026-98202. An attack has to be approached locally. There is no exploit available.
You should upgrade the affected component.
Details
A vulnerability, which was classified as problematic, has been found in Linux Kernel up to 7.3-rc3. Affected by this issue is the function rmi_driver_suspend/rmi_driver_resume of the component synaptics-rmi4. The manipulation with an unknown input leads to a null pointer dereference vulnerability. Using CWE to declare the problem leads to CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. Impacted is availability. CVE summarizes:
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 advisory is shared for download at git.kernel.org. This vulnerability is handled as CVE-2026-98202 since 09/25/2026. The exploitation is known to be easy. The attack needs to be approached locally. Successful exploitation requires user interaction by the victim. There are known technical details, but no exploit is available.
Upgrading to version 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112, 6.18.54, 7.2.8 or 7.3-rc4 eliminates this vulnerability. Applying the patch 7a3d7c68aa36f68e2a4824da4782c0e5d7c4eba4/fafca210631d8c2d4311bdfccc5ec46b9fe65977/84145a4a1dc58f8959811913c5f61f3235dd9f6c/e2b6703465c1ce43edb91c1626604b7092b3c431/30366f507ce3e408caf7f7375bb343df54b9a4f9/fa1713dc3d43d028d6cb66e5659d9d7e83b73362/942b06a19252908d0f952c0590caf20e47f88252/fe10579b6dc3f0dac61e51e1797cacbba5039ac2 is able to eliminate this problem. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2026-3743). Once again VulDB remains the best source for vulnerability data.
Affected
- Open Source Linux Kernel
Product
Type
Vendor
Name
Version
- 5.10.270
- 5.15.221
- 6.1.188
- 6.6.157
- 6.12.111
- 6.18.0
- 6.18.1
- 6.18.2
- 6.18.3
- 6.18.4
- 6.18.5
- 6.18.6
- 6.18.7
- 6.18.8
- 6.18.9
- 6.18.10
- 6.18.11
- 6.18.12
- 6.18.13
- 6.18.14
- 6.18.15
- 6.18.16
- 6.18.17
- 6.18.18
- 6.18.19
- 6.18.20
- 6.18.21
- 6.18.22
- 6.18.23
- 6.18.24
- 6.18.25
- 6.18.26
- 6.18.27
- 6.18.28
- 6.18.29
- 6.18.30
- 6.18.31
- 6.18.32
- 6.18.33
- 6.18.34
- 6.18.35
- 6.18.36
- 6.18.37
- 6.18.38
- 6.18.39
- 6.18.40
- 6.18.41
- 6.18.42
- 6.18.43
- 6.18.44
- 6.18.45
- 6.18.46
- 6.18.47
- 6.18.48
- 6.18.49
- 6.18.50
- 6.18.51
- 6.18.52
- 6.18.53
- 7.2.0
- 7.2.1
- 7.2.2
- 7.2.3
- 7.2.4
- 7.2.5
- 7.2.6
- 7.2.7
- 7.3-rc1
- 7.3-rc2
- 7.3-rc3
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.0VulDB Meta Temp Score: 4.8
VulDB Base Score: 5.0
VulDB Temp Score: 4.8
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Null pointer dereferenceCWE: CWE-476 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 5.10.271/5.15.222/6.1.189/6.6.158/6.12.112/6.18.54/7.2.8/7.3-rc4
Patch: 7a3d7c68aa36f68e2a4824da4782c0e5d7c4eba4/fafca210631d8c2d4311bdfccc5ec46b9fe65977/84145a4a1dc58f8959811913c5f61f3235dd9f6c/e2b6703465c1ce43edb91c1626604b7092b3c431/30366f507ce3e408caf7f7375bb343df54b9a4f9/fa1713dc3d43d028d6cb66e5659d9d7e83b73362/942b06a19252908d0f952c0590caf20e47f88252/fe10579b6dc3f0dac61e51e1797cacbba5039ac2
Timeline
09/25/2026 CVE reserved10/06/2026 Advisory disclosed
10/06/2026 VulDB entry created
10/07/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2026-98202 (🔒)
GCVE (CVE): GCVE-0-2026-98202
GCVE (VulDB): GCVE-100-414164
CERT Bund: WID-SEC-2026-3743 - Linux Kernel: Mehrere Schwachstellen
Entry
Created: 10/06/2026 13:19Updated: 10/07/2026 11:00
Changes: 10/06/2026 13:19 (59), 10/07/2026 11:00 (7)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.