In the Linux kernel, the following vulnerability has been resolved: i2c: imx-lpi2c: mark I2C adapter when hardware is powered down On some i.MX… (CVE-2026-64278)
A vulnerability in the Linux kernel's i2c imx-lpi2c driver could cause a system hang during suspend/resume cycles on some i.MX platforms. This occurs because I2C transfers may be attempted while hardware resources like clocks and pinctrl are disabled or not yet restored. The issue is resolved by marking the I2C adapter as suspended during the noirq suspend phase to block transfers until resume.
AI Analysis
Technical Summary
The Linux kernel i2c imx-lpi2c driver had a vulnerability where certain I2C client drivers with periodic workqueues could trigger I2C transfers during a critical window in system suspend/resume. In this window, hardware resources such as clocks and pinctrl may be disabled or not restored, causing attempts to access I2C registers when hardware is unavailable. This could lead to a system hang. The fix involves marking the I2C adapter as suspended during the noirq suspend phase and blocking new transfers until the system resumes, ensuring transfers only occur when hardware resources are available.
Potential Impact
The vulnerability can cause a system hang during suspend/resume operations on affected i.MX platforms due to attempts to access unavailable I2C hardware resources. There is no indication of code execution, data corruption, or privilege escalation. No known exploits are reported in the wild.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to mark the I2C adapter as suspended during the noirq suspend phase, blocking transfers until resume. Users should update to a Linux kernel version that includes this fix. Patch status is not explicitly confirmed in the provided data; users should consult the official Linux kernel advisories or vendor patches for the exact fixed versions and apply them accordingly.
In the Linux kernel, the following vulnerability has been resolved: i2c: imx-lpi2c: mark I2C adapter when hardware is powered down On some i.MX… (CVE-2026-64278)
Description
A vulnerability in the Linux kernel's i2c imx-lpi2c driver could cause a system hang during suspend/resume cycles on some i.MX platforms. This occurs because I2C transfers may be attempted while hardware resources like clocks and pinctrl are disabled or not yet restored. The issue is resolved by marking the I2C adapter as suspended during the noirq suspend phase to block transfers until resume.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel i2c imx-lpi2c driver had a vulnerability where certain I2C client drivers with periodic workqueues could trigger I2C transfers during a critical window in system suspend/resume. In this window, hardware resources such as clocks and pinctrl may be disabled or not restored, causing attempts to access I2C registers when hardware is unavailable. This could lead to a system hang. The fix involves marking the I2C adapter as suspended during the noirq suspend phase and blocking new transfers until the system resumes, ensuring transfers only occur when hardware resources are available.
Potential Impact
The vulnerability can cause a system hang during suspend/resume operations on affected i.MX platforms due to attempts to access unavailable I2C hardware resources. There is no indication of code execution, data corruption, or privilege escalation. No known exploits are reported in the wild.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to mark the I2C adapter as suspended during the noirq suspend phase, blocking transfers until resume. Users should update to a Linux kernel version that includes this fix. Patch status is not explicitly confirmed in the provided data; users should consult the official Linux kernel advisories or vendor patches for the exact fixed versions and apply them accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-mxwh-8xg9-m967
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64278"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a65420f9c2644c7f80868dc
Added to database: 07/25/2026, 23:09:03 UTC
Last enriched: 07/25/2026, 23:41:59 UTC
Last updated: 07/26/2026, 05:32:26 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.