CVE-2026-98204: Linux kernel · Input: rmi_smbus – fix out-of-bounds read in rmi_smb_write_block()
Affects Linux kernelSource GCVE Database
Not known to be exploited.
Data as of 28 Oct 2026, 01:27 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
Exploitation evidence
Disclosed: evidence found.
CVE published 6 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-azure-fdepkg:deb/ubuntu/linux-azure-fde?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-gkepkg:deb/ubuntu/linux-gke?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
In the Linux kernel, the following vulnerability has been resolved: Input: rmi_smbus - fix out-of-bounds read in rmi_smb_write_block() When chunking writes into SMBus blocks in rmi_smb_write_block(), the loop calculates block_len using the original total length (len) instead of the remaining length (cur_len). If len is greater than 32 bytes (SMB_MAX_COUNT), block_len remains 32 for every iteration, even on the final partial chunk where fewer than 32 bytes remain. This causes smb_block_write() to read 32 bytes from the advanced data buffer pointer, reading past the end of the input buffer. Fix this by calculating block_len using cur_len and advancing the buffer and address pointers by block_len.
References
- ubuntu.com/security/CVE-2026-98204 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-98204 (opens in a new tab)
- git.kernel.org/linus/51cfe54f815ae175c7d1126b983d4d7c89715004 (opens in a new tab)
- git.kernel.org/stable/c/29fbcf5834f0a7f74bfd017c07da2411b35a4e2a (opens in a new tab)
- git.kernel.org/stable/c/50dd585bee7669eb165e5defcc35d17f3822cfbb (opens in a new tab)
- git.kernel.org/stable/c/51cfe54f815ae175c7d1126b983d4d7c89715004 (opens in a new tab)
- git.kernel.org/stable/c/7c800af1c6030a5f27d46ce7d6d5d75f9c1efaf8 (opens in a new tab)
- git.kernel.org/stable/c/9f0ce5e162eed8b68345abe839c59768bc60f99a (opens in a new tab)
- git.kernel.org/stable/c/d01337c0892d1509500c727edf81380777c2dd0f (opens in a new tab)
- git.kernel.org/stable/c/dc05ec97b8299e48e31367a9bc412c7e9c0e2b42 (opens in a new tab)
- git.kernel.org/stable/c/e022538e13dd1c82af5ec25ac28f12ca0ab26160 (opens in a new tab)