CVE-2026-53340 i2c: imx: fix clock and pinctrl state inconsistency in runtime PM

Medium 5.5 Published Updated

A logic error in the i2c_imx driver's runtime power management can cause a system crash if pinctrl selection fails, leading to denial of service.

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

What is CVE-2026-53340?

CVE-2026-53340 is a medium-severity denial of service vulnerability in Linux kernel, published on 1 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: fix clock and pinctrl state inconsistency in runtime PM

In i2c_imx_runtime_suspend(), the clock is disabled before switching the pinctrl state to sleep. If pinctrl_pm_select_sleep_state() fails, the runtime suspend is aborted but the clock remains disabled, causing a system crash when the hardware is subsequently accessed.

Fix this by switching the pinctrl state before disabling the clock so that a pinctrl failure leaves the clock enabled and the hardware accessible.

In i2c_imx_runtime_resume(), restore the pinctrl state back to sleep if clk_enable() fails to keep the consistent.

Which versions are affected by CVE-2026-53340?

It affects 1 product.

Products include Linux kernel.

How do I fix CVE-2026-53340?

Apply the vendor's patch.

Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.

Is CVE-2026-53340 being exploited?

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

All Linux kernel vulnerabilities

Sources

Also known as BELL-CVE-2026-53340, DEBIAN-CVE-2026-53340, GHSA-4fhj-6vjr-7222, UBUNTU-CVE-2026-53340.

Is CVE-2026-53340 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free