Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-98204 Overview
CVE-2026-98204 is an out-of-bounds read vulnerability in the Linux kernel's rmi_smbus input driver. The flaw resides in the rmi_smb_write_block() function, which chunks writes into System Management Bus (SMBus) blocks for Synaptics RMI4 devices. The loop incorrectly calculates block_len using the original total length (len) instead of the remaining length (cur_len). When the input buffer exceeds 32 bytes (SMB_MAX_COUNT), the final partial chunk causes smb_block_write() to read 32 bytes from a buffer that holds fewer remaining bytes, reading past the end of the input buffer.
Critical Impact
The flaw triggers out-of-bounds memory reads in kernel space during legitimate RMI4 touchpad write operations, potentially leaking adjacent kernel memory contents to the SMBus transaction.
Affected Products
- Linux kernel versions containing the rmi_smbus driver prior to the referenced stable fixes
- Systems using Synaptics RMI4-based input devices (touchpads, touchscreens) over SMBus
- Multiple stable kernel branches patched via commits 29fbcf5, 50dd585, 51cfe54, 7c800af, 9f0ce5e, d01337c, dc05ec9, and e022538
Discovery Timeline
- 2026-10-06 - CVE-2026-98204 published to the National Vulnerability Database (NVD)
- 2026-10-06 - Last updated in NVD database
Technical Details for CVE-2026-98204
Vulnerability Analysis
The rmi_smb_write_block() function in drivers/input/rmi4/rmi_smbus.c splits writes larger than SMB_MAX_COUNT (32 bytes) into multiple SMBus block transactions. The chunking loop computes block_len = min(len, SMB_MAX_COUNT) using the original write size rather than the remaining byte count tracked by cur_len. On every iteration, including the final partial chunk, block_len stays fixed at 32. The downstream smb_block_write() call then reads 32 bytes from the advanced buffer pointer, overrunning the caller-supplied buffer whenever len is not an exact multiple of 32.
The out-of-bounds read occurs in kernel memory. Depending on heap layout, adjacent data is transmitted over the SMBus to the connected RMI4 device. This creates both an information disclosure surface and a reliability concern, as the kernel may touch unmapped or sensitive memory.
Root Cause
The root cause is an incorrect length variable in the chunking loop [CWE-125, Out-of-Bounds Read]. The fix recalculates block_len on each iteration using cur_len, the number of bytes still to be written, and advances the buffer and address pointers by that corrected block_len value.
Attack Vector
Triggering the condition requires issuing an RMI4 SMBus write whose total length exceeds 32 bytes and is not a multiple of 32. This typically requires local access to a system with an attached Synaptics RMI4 touchpad or touchscreen bound to the rmi_smbus driver. Remote exploitation is not applicable. The vulnerability does not provide direct code execution. See the referenced kernel git commits for the exact patch diff and reproduction context.
Detection Methods for CVE-2026-98204
Indicators of Compromise
- No specific runtime indicators of compromise are published for this out-of-bounds read; exploitation typically manifests as abnormal SMBus traffic or KASAN splats in kernel logs.
- KASAN: slab-out-of-bounds in rmi_smb_write_block or similar messages in dmesg on kernels built with KASAN enabled.
Detection Strategies
- Inventory kernel versions across Linux endpoints and servers and compare against the fixed commits (29fbcf5, 50dd585, 51cfe54, 7c800af, 9f0ce5e, d01337c, dc05ec9, e022538).
- Enable Kernel Address Sanitizer (KASAN) in test environments to surface the out-of-bounds read during RMI4 driver exercise.
- Monitor kernel ring buffer logs for rmi_smbus or rmi4 warnings using centralized log collection.
Monitoring Recommendations
- Forward /var/log/kern.log and journald kernel facility events to a centralized logging platform for correlation.
- Track package and kernel update status across the fleet to confirm patched builds are deployed.
- Alert on unexpected RMI4 device bind or probe events on servers and virtualized workloads where such hardware should not be present.
How to Mitigate CVE-2026-98204
Immediate Actions Required
- Apply the stable kernel updates that include the referenced fix commits for the rmi_smbus driver.
- Reboot affected systems after kernel package installation to load the patched image.
- Prioritize laptops and workstations with Synaptics RMI4 touchpads attached over SMBus.
Patch Information
The fix recalculates block_len from the remaining byte count (cur_len) and advances the buffer and address pointers by block_len each iteration. Patches have been merged into multiple stable branches. Refer to the upstream commits: Kernel Git Commit 29fbcf5, Kernel Git Commit 50dd585, Kernel Git Commit 51cfe54, Kernel Git Commit 7c800af, Kernel Git Commit 9f0ce5e, Kernel Git Commit d01337c, Kernel Git Commit dc05ec9, and Kernel Git Commit e022538.
Workarounds
- On systems without Synaptics RMI4 SMBus hardware, blacklist the rmi_smbus module via /etc/modprobe.d/ to prevent accidental load.
- Where the driver is required, limit untrusted local access to the system until the patched kernel is deployed.
- Avoid custom userspace tooling that issues oversized RMI4 writes until kernels are updated.
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

