Local kernel compromise via oversized I2C block transfer
Published Jul 20, 2026 · Updated Jul 20, 2026
Out-of-bounds access in the Linux Kernel i2c-stub driver allows local users to corrupt or disclose kernel memory through an I2C ioctl. stub_xfer() trusts data->block[0] above the 32-byte limit and copies past the stack-resident i2c_smbus_data.block buffer because its direct smbus_xfer path bypasses validation. The nondefault i2c-stub module must be loaded with chip_addr, and the attacker needs access to its /dev/i2c-* node; exploitation can disclose kernel-stack data, panic the host, or execute kernel code.
Summary
What happened
Out-of-bounds access in the Linux Kernel i2c-stub driver allows local users to corrupt or disclose kernel memory through an I2C ioctl. stub_xfer() trusts data->block[0] above the 32-byte limit and copies past the stack-resident i2c_smbus_data.block buffer because its direct smbus_xfer path bypasses validation. The nondefault i2c-stub module must be loaded with chip_addr, and the attacker needs access to its /dev/i2c-* node; exploitation can disclose kernel-stack data, panic the host, or execute kernel code.
The record
- CVE
- CVE-2026-64191
- Published
- Jul 20, 2026
- Updated
- Jul 20, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-125, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 20, 2026CVE publishedPublication date reported by the CVE source.
- Jul 20, 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=2.6.33
- Affected versionversion=4710317891e4824ce1510a6b5066abbd3e917750 <0526931b16e5a118d367b7bfce7d797e63f7ac69
- Affected versionversion=4710317891e4824ce1510a6b5066abbd3e917750 <1c4ffe6b4f04365485ed58d64c9bb86b46fc9037
- Affected versionversion=4710317891e4824ce1510a6b5066abbd3e917750 <21e87f336ac6303fed54a69b1d0d79a23b25c8d0
- Affected versionversion=4710317891e4824ce1510a6b5066abbd3e917750 <3fd225f3e4cd67ec8ddab1afed9da03c7c43537c
- Affected versionversion=4710317891e4824ce1510a6b5066abbd3e917750 <4bd8635f28c135a08aac6badcd7d9b5cdb34335f
- Affected versionversion=4710317891e4824ce1510a6b5066abbd3e917750 <5f4d2bd028ebb6e4c09a9d64842546022321d4a7
- Affected versionversion=4710317891e4824ce1510a6b5066abbd3e917750 <6036b5067a8199ba7a2dc7b377d4b9dd276d5f9e
- Affected versionversion=4710317891e4824ce1510a6b5066abbd3e917750 <7e9072dbd5f2f17934751873450d2c22080ead80
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