Out-of-bounds SRAM access via wrong SPI geometry
Published Aug 15, 2026 · Updated Aug 15, 2026
Out-of-bounds SRAM access in the Linux kernel allows local users to read or corrupt unintended chip data through MTD I/O. During mchp23k256 probe, of_device_get_match_data() ignores SPI ID-table driver_data when no OF match exists and applies 32-KiB, two-byte-address geometry to a 128-KiB mchp23lcv1024 part. The path requires local access to /dev/mtdN on a non-OF, SPI-ID-only deployment; crafted reads disclose other SRAM regions, while writes corrupt them and can stall the SPI bus or crash embedded services.
Summary
What happened
Out-of-bounds SRAM access in the Linux kernel allows local users to read or corrupt unintended chip data through MTD I/O. During mchp23k256 probe, of_device_get_match_data() ignores SPI ID-table driver_data when no OF match exists and applies 32-KiB, two-byte-address geometry to a 128-KiB mchp23lcv1024 part. The path requires local access to /dev/mtdN on a non-OF, SPI-ID-only deployment; crafted reads disclose other SRAM regions, while writes corrupt them and can stall the SPI bus or crash embedded services.
The record
- CVE
- CVE-2026-68467
- Published
- Aug 15, 2026
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-348, T1005, T1565.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 15, 2026CVE publishedPublication date reported by the CVE source.
- Aug 15, 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.13
- Affected versionversion=4379075a870b8de43a9ecd5b46884953234fc669 <04ebd3766861f219325852c9598e0f0281cb3636
- Affected versionversion=4379075a870b8de43a9ecd5b46884953234fc669 <09e044192a42f716215fbd1a100ee87fa57426aa
- Affected versionversion=4379075a870b8de43a9ecd5b46884953234fc669 <2e179b028da9fd628a09286a2c9df4fa076b2cc9
- Affected versionversion=4379075a870b8de43a9ecd5b46884953234fc669 <7c0a3a73dccc9a3fc701f6be762449f18d0ca0fc
- Affected versionversion=4379075a870b8de43a9ecd5b46884953234fc669 <a0c38083623c8b210a5b87fd34bebd05aa935ae8
- Affected versionversion=4379075a870b8de43a9ecd5b46884953234fc669 <d322e40f4edf92bf0ca329e5aa4ae1c0316feb38
- Affected versionversion=4379075a870b8de43a9ecd5b46884953234fc669 <dbe2254d1da99c986f9a3392471fc5eaa3229647
What conditions does exploitation require?
What is affected?
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