Kernel crash via unchecked I2C device match data
Published May 1, 2024 · Updated May 23, 2026
NULL pointer dereference in affected Linux kernels allows local users to crash the kernel via max14830 I2C instantiation. The max310x_i2c_probe function treats missing device match data as a devtype pointer and dereferences it while validating the client address. Reaching the flaw requires local permission to create an I2C device through sysfs, and successful triggering interrupts availability through a kernel oops.
Summary
What happened
NULL pointer dereference in affected Linux kernels allows local users to crash the kernel via max14830 I2C instantiation. The max310x_i2c_probe function treats missing device match data as a devtype pointer and dereferences it while validating the client address. Reaching the flaw requires local permission to create an I2C device through sysfs, and successful triggering interrupts availability through a kernel oops.
The record
- CVE
- CVE-2024-26978
- Published
- May 1, 2024
- Updated
- May 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 1, 2024CVE publishedPublication date reported by the CVE source.
- May 23, 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=2e1f2d9a9bdbe12ee475c82a45ac46a278e8049a <0d27056c24efd3d63a03f3edfbcfc4827086b110
- Affected versionversion=2e1f2d9a9bdbe12ee475c82a45ac46a278e8049a <12609c76b755dbeb1645c0aacc0f0f4743b2eff3
- Affected versionversion=2e1f2d9a9bdbe12ee475c82a45ac46a278e8049a <2160ad6861c4a21d3fa553d7b2aaec6634a37f8a
- Affected versionversion=2e1f2d9a9bdbe12ee475c82a45ac46a278e8049a <5cd8af02b466e1beeae13e2de3dc58fcc7925e5a
- Affected versionversion=2e1f2d9a9bdbe12ee475c82a45ac46a278e8049a <aeca49661fd02fd56fb026768b580ce301b45733
- Affected versionversion=5.10.213 <5.10.215
- Affected versionversion=5.4.272 <5.4.274
- Affected versionversion=6.0
- Affected versionversion=85d79478710ad2cbf11857aec107084a7104943e <c45e53c27b78afd6c81fc25608003576f27b5735
- Affected versionversion=f5c252aaa1be5d38604e58e9bd335065f767d0d8 <7d271b798add90c6196539167c019d0817285cf0
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
- max14830 userspace I2C instantiation reproducerproof of concept · demonstrated
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