CVE-2026-98204
Input: rmi_smbus - fix out-of-bounds read in rmi_smb_write_block()
No known exploitation. EPSS puts it in the 7th percentile. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- LinuxAffected: ≥ 82264d0cf7aef2247563c031ff2ab96579d5d0cc, < d01337c0892d1509500c727edf81380777c2dd0fUpgrade to: d01337c0892d1509500c727edf81380777c2dd0fAffected: ≥ 82264d0cf7aef2247563c031ff2ab96579d5d0cc, < 7c800af1c6030a5f27d46ce7d6d5d75f9c1efaf8Upgrade to: 7c800af1c6030a5f27d46ce7d6d5d75f9c1efaf8Affected: ≥ 82264d0cf7aef2247563c031ff2ab96579d5d0cc, < 29fbcf5834f0a7f74bfd017c07da2411b35a4e2aUpgrade to: 29fbcf5834f0a7f74bfd017c07da2411b35a4e2aAffected: ≥ 82264d0cf7aef2247563c031ff2ab96579d5d0cc, < 50dd585bee7669eb165e5defcc35d17f3822cfbbUpgrade to: 50dd585bee7669eb165e5defcc35d17f3822cfbb + 4 more branchesStated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
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.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.2% chance of exploitation activity in the next 30 days, which ranks it in the 7th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
2 events over 0 days, from the signal feeds we watch.
- Publishedrecord updated
Affected products
Sources
References in the record
- git.kernel.org/stable/c/29fbcf5834f0a7f74bfd017c07da2411b35a4e2a
- git.kernel.org/stable/c/50dd585bee7669eb165e5defcc35d17f3822cfbb
- git.kernel.org/stable/c/51cfe54f815ae175c7d1126b983d4d7c89715004
And 5 more references. See all after sign-in
In the news
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Linux, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI