Kernel memory corruption via I2C registration race
Published Jul 19, 2026 · Updated Jul 19, 2026
Race condition in the Linux Kernel I2C core allows local users to corrupt kernel memory or escalate privileges during adapter registration. The registration path publishes an adapter in the IDR before initializing its embedded struct device, so concurrent i2c_get_adapter() calls can reference uninitialized data and trigger use-after-free or a NULL-pointer dereference. A low-privileged local user needs I2C device access, module-loading capability in a user namespace, or control of hotplug while racing adapter lookup; success grants kernel-level access or crashes the system.
Summary
What happened
Race condition in the Linux Kernel I2C core allows local users to corrupt kernel memory or escalate privileges during adapter registration. The registration path publishes an adapter in the IDR before initializing its embedded struct device, so concurrent i2c_get_adapter() calls can reference uninitialized data and trigger use-after-free or a NULL-pointer dereference. A low-privileged local user needs I2C device access, module-loading capability in a user namespace, or control of hotplug while racing adapter lookup; success grants kernel-level access or crashes the system.
The record
- CVE
- CVE-2026-53400
- Published
- Jul 19, 2026
- Updated
- Jul 19, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-362, CWE-824, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 19, 2026CVE publishedPublication date reported by the CVE source.
- Jul 19, 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.22
- Affected versionversion=6e13e641841833cc2aa5baefe89bb04bc388801b <6a946038f2a5a8c29048c6af369d4e391448a5c5
- Affected versionversion=6e13e641841833cc2aa5baefe89bb04bc388801b <78793c75dc6d0ff2e4d50ad617349b328a99054e
- Affected versionversion=6e13e641841833cc2aa5baefe89bb04bc388801b <a4c8094bbf4c6fa68b17e3b16f6a0a1b7a14f3e0
- Affected versionversion=6e13e641841833cc2aa5baefe89bb04bc388801b <ba14d7cf2fe7284610a29854bdff22b2537d3ce6
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