Kernel memory corruption via unchecked effect index
Published Jul 25, 2026 · Updated Jul 25, 2026
Out-of-bounds write in the iforce input driver in Linux Kernel allows physically proximate attackers to corrupt kernel memory via a crafted device. iforce_process_packet() masks status byte data[1] to seven bits but uses values up to 127 to index the 32-entry core_effects array, causing a single-bit read-modify-write beyond the object. Access requires a malicious or counterfeit USB or serio device; well-formed devices remain within bounds, while malformed status packets can corrupt adjacent kernel state.
Summary
What happened
Out-of-bounds write in the iforce input driver in Linux Kernel allows physically proximate attackers to corrupt kernel memory via a crafted device. iforce_process_packet() masks status byte data[1] to seven bits but uses values up to 127 to index the 32-entry core_effects array, causing a single-bit read-modify-write beyond the object. Access requires a malicious or counterfeit USB or serio device; well-formed devices remain within bounds, while malformed status packets can corrupt adjacent kernel state.
The record
- CVE
- CVE-2026-64273
- Published
- Jul 25, 2026
- Updated
- Jul 25, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-129, CWE-787, T1200
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 25, 2026CVE publishedPublication date reported by the CVE source.
- Jul 25, 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0e9943d2e4c63496b6ca84bc66fd3c71d40558e2
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6c0f2901c9d325d4a0574c4237fd507810d225ff
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <70019779325f2bb5f5a4098e91e79c655f50fcef
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a40250f97c312e000e3616c9074022311a0efbc3
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b1b79e89bc33e4c682d3df7ae2aadc62b5a0c310
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c21295616a8a52b9a5f18cd4ca8c73030eda3d4f
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d10b0507fa0f5b46764b178e3271f9012f2df677
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e5fa31f0550b55d80045669ae9080dd5b88abffa
- Affected versionversion=2.6.12
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.
Weakness, pattern, technique
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