Skip to main content

Linux Kernel EUVDEUVD-2026-48990

| CVE-2026-64278 MEDIUM
2026-07-25 Linux GHSA-mxwh-8xg9-m967
Information Disclosure Linux
5.5
CVSS 3.1 · NVD
Share

Severity by source

NVD PRIMARY
5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
vuln.today AI
5.5 MEDIUM

Local race condition during suspend/resume requires low-privilege local access; no confidentiality or integrity impact, only availability via system hang.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
4.0 AV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
SUSE
MEDIUM
qualitative

Primary rating from NVD.

CVSS VectorNVD

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

5
Analysis Generated
Aug 13, 2026 - 18:41 vuln.today
CVSS changed
Aug 13, 2026 - 18:37 NVD
5.5 (MEDIUM)
Patch available
Jul 25, 2026 - 11:18 EUVD
CVE Published
Jul 25, 2026 - 08:49 nvd
MEDIUM 5.5
CVE Published
Jul 25, 2026 - 08:49 cve.org
UNKNOWN (no severity yet)

DescriptionNVD

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.

AnalysisAI

System hang vulnerability in the Linux kernel's NXP i.MX LPI2C driver arises from a race condition during suspend/resume power transitions. Specifically, periodic workqueues in I2C client drivers can fire I2C transfers between the suspend_noirq and resume_noirq phases, when clock and pinctrl resources have already been disabled or are not yet restored. Accessing I2C controller registers in this state causes the system to hang. The fix marks the adapter as suspended during noirq suspend, blocking transfers until hardware resources are fully restored. No public exploit or confirmed active exploitation (CISA KEV) has been identified at time of analysis.

Technical ContextAI

The affected component is the LPI2C (Low Power I2C) controller driver for NXP i.MX SoCs, found in drivers/i2c/busses/imx-lpi2c.c in the Linux kernel. LPI2C is a hardware I2C peripheral integrated into i.MX application processors used widely in embedded and automotive platforms. The root cause is a classic TOCTOU-class race in power management: the driver does not gate I2C transfers against the hardware power state. During Linux kernel suspend, the noirq phase runs after devices are powered down or clocked off, yet kernel workqueue threads (kworker) may not be frozen in this narrow window. No CWE was formally assigned; the closest applicable classifications are CWE-362 (Concurrent Execution Using Shared Resource with Improper Synchronization) and CWE-822 (Untrusted Pointer Dereference due to absent state check). CPE data identifies the affected software as cpe:2.3:a:linux:linux:*:*:*:*:*:*:*:*, specifically from the introduction of the vulnerable code at commit 1ee867e465c1b0216ec02d4c0d334c4e89919cec.

RemediationAI

The primary fix is to upgrade to a patched kernel version: Linux 6.18.39 (stable branch), Linux 7.1.4 (stable branch), or Linux 7.2-rc1 (mainline). Upstream fix commits are available at https://git.kernel.org/stable/c/b2523f26979e0b5bd1422772176b2233fcd1f6d0, https://git.kernel.org/stable/c/5800647d19d3f1f747fda4dc67e55d6afa6ee119, and https://git.kernel.org/stable/c/218cfe364b55b2768221629bd4a69ad190b7fbbc. If immediate kernel upgrade is not feasible, a compensating control is to disable or prevent the periodic workqueue in the affected I2C client driver that continues to issue transfers during suspend - this may require modifying the client driver's suspend callback to cancel the workqueue before the noirq phase, though this has the trade-off of requiring application-level changes. Alternatively, configuring the system to freeze workqueue threads before the noirq phase (if platform-specific kernel options allow) reduces the race window. Distribution-specific updates from vendors shipping i.MX-targeted Linux (e.g., Yocto/meta-imx or NXP BSP) should be monitored for backported patches.

Same technique Information Disclosure

View all
CVE-2019-2725 CRITICAL POC
9.8
CVE-2021-34523 CRITICAL POC
9.0
CVE-2013-2251 CRITICAL POC
9.8
CVE-2017-5638 CRITICAL POC
9.8
CVE-2025-24813 CRITICAL POC
9.8
CVE-2015-1701 HIGH POC
7.8
CVE-2017-0147 HIGH POC
7.5
CVE-2014-6324 HIGH POC
8.8

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
openSUSE Tumbleweed Fixed
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected

Share

EUVD-2026-48990 vulnerability details – vuln.today
Back

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy