Kernel crash via unchecked I2C block length
Published Apr 20, 2023 · Updated Apr 23, 2025
Out-of-bounds write in Linux Kernel before 6.3-rc4 allows local users with SLIMpro I2C device access to crash the system. The slimpro_i2c_blkwr path passes an unchecked user-derived data->block[0] length to memcpy, which writes beyond dma_buffer. Access to the device requires elevated privileges; a kernel crash is documented, while reliable code execution remains unconfirmed.
Summary
What happened
Out-of-bounds write in Linux Kernel before 6.3-rc4 allows local users with SLIMpro I2C device access to crash the system. The slimpro_i2c_blkwr path passes an unchecked user-derived data->block[0] length to memcpy, which writes beyond dma_buffer. Access to the device requires elevated privileges; a kernel crash is documented, while reliable code execution remains unconfirmed.
The record
- CVE
- CVE-2023-2194
- Published
- Apr 20, 2023
- Updated
- Apr 23, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-787, T1499.004
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Apr 20, 2023CVE publishedPublication date reported by the CVE source.
- Apr 23, 2025Record 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=Fixed in kernel v6.3-rc4
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo