dbcve.org
Linux KernelOperating system · Linux

CVE-2026-53340

MEDIUM · 5.5 CVSS v3.1 Published 2026-07-01
Fix available
A fix is available. Upgrade to 6.18.36 / 7.0.13 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click Patch available 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In the Linux kernel's I2C imx driver, the runtime PM suspend sequence incorrectly disables the clock before switching the pinctrl state to sleep. If pinctrl_pm_select_sleep_state() fails, the suspend aborts but the clock remains disabled, causing a system crash when hardware is subsequently accessed. The fix reorders operations so pinctrl is changed before clock disable, and in resume, pinctrl is restored to sleep state if clock enable fails.

MitigationApply the kernel patch which reorders the pinctrl and clock operations in i2c_imx_runtime_suspend() and i2c_imx_runtime_resume(), or update to a kernel version containing this fix.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 6.14, < 6.18.36>= 6.19, < 7.0.13= 7.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check kernel version against affected range
    Run `uname -r` or read `/proc/version` to get the kernel version. Compare against: >= 6.14, < 6.18.36; >= 6.19, < 7.0.13; = 7.1
    Affected if Kernel version falls within any of the affected version ranges
  2. Verify i2c-imx driver is in use
    Check for i2c-imx device or driver: look in `/sys/bus/platform/devices/*/driver` for entries containing 'imx-i2c' or run `lsmod | grep i2c_imx`
    Affected if The i2c-imx driver is loaded and managing devices on the system
  3. Confirm runtime PM is enabled for i2c-imx devices
    Check runtime PM status: `cat /sys/bus/platform/devices/*/power/control` for i2c-imx devices, or check `/sys/devices/platform/*-i2c*/power/control` - look for 'auto' (enabled) rather than 'on' (disabled)
    Affected if Runtime PM is set to 'auto' for i2c-imx devices, enabling the vulnerable suspend/resume code paths
  4. Inspect driver source for vulnerable code order
    If driver source is available, examine `i2c_imx_runtime_suspend()` and `i2c_imx_runtime_resume()` functions in the i2c-imx driver - check if clock operations occur before pinctrl operations in suspend path
    Affected if The driver code shows clock disable/enable happening before pinctrl state switch in the runtime suspend/resume functions

A system is affected if it runs a vulnerable kernel version AND uses the i2c-imx driver with runtime PM enabled, where the driver code has the original unsafe ordering of clock and pinctrl operations.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.18.36 / 7.0.13 or later
Fixed in 6.18.367.0.13
Vendor patch git.kernel.org →
Interim mitigation

Apply the kernel patch which reorders the pinctrl and clock operations in i2c_imx_runtime_suspend() and i2c_imx_runtime_resume(), or update to a kernel version containing this fix.

Recommended fix High confidence

6.18.36+, 7.0.13+, or 7.2+ (depending on which branch you are on)

  1. Identify current kernel version using `uname -r` or `cat /proc/version`
  2. Upgrade to Linux kernel version 6.18.36 or later if using the 6.14-6.18.x branch
  3. Upgrade to Linux kernel version 7.0.13 or later if using the 6.19-7.0.x branch
  4. Upgrade to Linux kernel version 7.2 or later if using the 7.1.x branch
  5. Reboot the system to load the fixed kernel
Caveat Kernel upgrades may introduce regressions; test in staging environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,904.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53340 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-53340 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data