CVE-2026-68464
mmc: sdhci-esdhc-imx: disable irq during suspend to fix unhandled interrupt
Reported by linux · Published August 15, 2026
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.
EPSS 0.21% · 10.7th percentile
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| Linux | Linux | 9d87eaf985cef9581b6ed99b461b38e8cd666480, 9bf4ee05a1109d889de9151ee78bd80293923f70, 4f96903e2fd228aa96013372402d650f6dbe5cb3 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 676a83855614635af3bf31ad3f8fec4031f81354, 676a83855614635af3bf31ad3f8fec4031f81354, 676a83855614635af3bf31ad3f8fec4031f81354 |
| Linux | Linux | 6.16, 0, 6.18.40 |
| Linux | Linux | 7.2, 0, 6.18.40 |
| linux | linux_kernel | 6.16, 6.16, 6.16 |
Timeline
- Aug 15, 2026 Coalition ESS Score
- Aug 15, 2026 CVE Published
- Aug 17, 2026 CVE Updated
- Aug 19, 2026 Security Advisory
- Aug 24, 2026 EPSS Score (14 in total, the first dated here)
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-68464
vulnetix vdb fixes CVE-2026-68464
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-68464/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart