Kernel buffer over-read via incorrect SMBus chunk length
Published Oct 6, 2026 · Updated Oct 6, 2026
Out-of-bounds read in the Linux kernel RMI SMBus input driver allows attackers to trigger a buffer over-read during SMBus writes. In rmi_smb_write_block(), the loop sizes the final block from the original write length rather than the remaining length, so smb_block_write() reads beyond the advanced input buffer. The path requires an RMI SMBus device and a write ending in a partial block; the public record documents neither an attacker-accessible trigger nor resulting data exposure.
Summary
What happened
Out-of-bounds read in the Linux kernel RMI SMBus input driver allows attackers to trigger a buffer over-read during SMBus writes. In rmi_smb_write_block(), the loop sizes the final block from the original write length rather than the remaining length, so smb_block_write() reads beyond the advanced input buffer. The path requires an RMI SMBus device and a write ending in a partial block; the public record documents neither an attacker-accessible trigger nor resulting data exposure.
The record
- CVE
- CVE-2026-98204
- Published
- Oct 6, 2026
- Updated
- Oct 6, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 6, 2026CVE publishedPublication date reported by the CVE source.
- Oct 6, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.10
- Affected versionversion=82264d0cf7aef2247563c031ff2ab96579d5d0cc <29fbcf5834f0a7f74bfd017c07da2411b35a4e2a
- Affected versionversion=82264d0cf7aef2247563c031ff2ab96579d5d0cc <50dd585bee7669eb165e5defcc35d17f3822cfbb
- Affected versionversion=82264d0cf7aef2247563c031ff2ab96579d5d0cc <51cfe54f815ae175c7d1126b983d4d7c89715004
- Affected versionversion=82264d0cf7aef2247563c031ff2ab96579d5d0cc <7c800af1c6030a5f27d46ce7d6d5d75f9c1efaf8
- Affected versionversion=82264d0cf7aef2247563c031ff2ab96579d5d0cc <9f0ce5e162eed8b68345abe839c59768bc60f99a
- Affected versionversion=82264d0cf7aef2247563c031ff2ab96579d5d0cc <d01337c0892d1509500c727edf81380777c2dd0f
- Affected versionversion=82264d0cf7aef2247563c031ff2ab96579d5d0cc <dc05ec97b8299e48e31367a9bc412c7e9c0e2b42
- Affected versionversion=82264d0cf7aef2247563c031ff2ab96579d5d0cc <e022538e13dd1c82af5ec25ac28f12ca0ab26160
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started