# CVE-2026-64278: i2c: imx-lpi2c: mark I2C adapter when hardware is powered down

> A race condition in the i.MX LPI2C driver during system suspend/resume can cause a system hang if I2C transfers are attempted while hardware resources are unavailable.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Jul 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-64278, DEBIAN-CVE-2026-64278, GHSA-mxwh-8xg9-m967, ROOT-OS-UBUNTU-2204-CVE-2026-64278, UBUNTU-CVE-2026-64278

## What is CVE-2026-64278?

CVE-2026-64278 is a medium-severity denial of service vulnerability in Linux kernel, published on 25 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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 platforms, certain I2C client drivers keep a periodic
workqueue which continues to trigger I2C transfers.

During system suspend/resume, there exists a time window between:
  - suspend_noirq and the system entering suspend
  - the system starting to resume and resume_noirq

In this window, the I2C controller resources such as clock and pinctrl
may already be disabled or not yet restored.

If a workqueue triggers an I2C transfer in this period, the driver
attempts to access I2C registers while the hardware resources are
unavailable, which may lead to system hang.

Mark the I2C adapter as suspended during noirq suspend and block new
transfers until resume, ensuring that I2C transfers are only issued
when hardware resources are available.

## Which versions are affected by CVE-2026-64278?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2026-64278?

Apply the vendor's patch.

## Is CVE-2026-64278 being exploited?

There is no known exploitation of CVE-2026-64278 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-64278 and fix it if it is affected.

What it is: CVE-2026-64278 is a medium-severity denial of service vulnerability in Linux kernel, published on 25 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-64278 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-64278/ (Markdown: https://insights.sbomify.com/CVE-2026-64278/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-64278
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-64278
- OSV: https://osv.dev/vulnerability/CVE-2026-64278

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-64278/
Summaries are generated and may contain mistakes; the official description above is the record.