Description
In the Linux kernel, the following vulnerability has been resolved:

mmc: sdhci-esdhc-imx: disable irq during suspend to fix unhandled interrupt

When using WIFI out-of-band wakeup, an "irq xxx: nobody cared" warning
occurs. This happens because the usdhc interrupt is not disabled during
system suspend when device_may_wakeup() returns false.

The sequence of events leading to this issue:
1. System enters suspend without disabling usdhc interrupt
(because device_may_wakeup() returns false for usdhc device)
2. WIFI out-of-band wakeup triggers system resume via GPIO interrupt
3. WIFI sends a Card interrupt before usdhc has fully resumed
4. usdhc is still in runtime suspend state and cannot handle the
interrupt properly
5. The unhandled interrupt triggers "nobody cared" warning

Fix this by unconditionally disabling the usdhc interrupt during suspend
and re-enabling it during resume, regardless of the wakeup capability.
This ensures no interrupts are processed during the suspend/resume
transition.
Published: 2026-08-15
Score: n/a
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The kernel driver for the SDHCI ESdhc imx controller fails to disable the uSDHC interrupt when the system enters suspend if the device cannot wake the system. When WiFi performs an out‑of‑band wake‑up, the hardware sends a Card interrupt before the uSDHC has fully resumed. Because the interrupt line remains active, the driver receives an IRQ that it cannot handle, which results in a "irq xxx: nobody cared" warning. This is an interrupt‑handling flaw that can destabilise the operating system and potentially cause a denial of service or a crash if the unhandled interrupt propagates further.

Affected Systems

All Linux kernel versions containing the older sdhci‑esdhc‑imx driver prior to the commit that disables the interrupt during suspend are affected. Since the exact version range is not published, any kernel build that predates commit 4f96903e2fd228aa96013372402d650f6dbe5cb3 is considered vulnerable.

Risk and Exploitability

The CVSS score is not provided and the EPSS score is unavailable; the vulnerability is not listed in the CISA KEV catalog. Exploitation would require the system to be in suspend state and the WiFi interface to perform an out‑of‑band wake‑up, so the attack surface is limited. Nonetheless, because the bug can be triggered automatically by normal hardware operation and produces a warning and possible instability, the risk is considered moderate rather than critical.

Generated by OpenCVE AI on August 15, 2026 at 08:11 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply a kernel update that includes commit 4f96903e2fd228aa96013372402d650f6dbe5cb3, which unconditionally disables the uSDHC interrupt during suspend and re‑enables it on resume.
  • If a kernel update is not possible, disable or suppress the WiFi out‑of‑band wake‑up feature to prevent the interrupt from being triggered while the system is suspended.
  • Alternatively, configure the system to avoid entering suspend mode while the SDHCI controller is in use, ensuring the interrupt is not active during transitions.

Generated by OpenCVE AI on August 15, 2026 at 08:11 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sat, 15 Aug 2026 08:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-362

Sat, 15 Aug 2026 06:00:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: mmc: sdhci-esdhc-imx: disable irq during suspend to fix unhandled interrupt When using WIFI out-of-band wakeup, an "irq xxx: nobody cared" warning occurs. This happens because the usdhc interrupt is not disabled during system suspend when device_may_wakeup() returns false. The sequence of events leading to this issue: 1. System enters suspend without disabling usdhc interrupt (because device_may_wakeup() returns false for usdhc device) 2. WIFI out-of-band wakeup triggers system resume via GPIO interrupt 3. WIFI sends a Card interrupt before usdhc has fully resumed 4. usdhc is still in runtime suspend state and cannot handle the interrupt properly 5. The unhandled interrupt triggers "nobody cared" warning Fix this by unconditionally disabling the usdhc interrupt during suspend and re-enabling it during resume, regardless of the wakeup capability. This ensures no interrupts are processed during the suspend/resume transition.
Title mmc: sdhci-esdhc-imx: disable irq during suspend to fix unhandled interrupt
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-08-15T05:51:23.578Z

Reserved: 2026-07-30T09:28:09.396Z

Link: CVE-2026-68464

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-15T06:19:25.430

Modified: 2026-08-15T06:19:25.430

Link: CVE-2026-68464

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-15T08:15:04Z

Weaknesses
  • CWE-362

    Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')