Skip to content
Heist/ feed
Back to feed
UnratedFix available

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

Type: advisorySources: OSV

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.

Products
Kernel
Affected versions
Not specified
Fixed versions
6.18.40, 7.1.5
CVEs
CVE-2026-68464
Confirmed fixed CVEs
Not specified
Updated in this feed
6 Nov 2026, 02:36 UTC · Revision 1

Source evidence

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

core-osv · Original source

Published 15 Aug 2026, 05:51 UTC

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.

osv:CVE-2026-68464

Kernel

Fixed versions: 6.18.40, 7.1.5

Complete source record
{
  "id": "02237d0810a39619dddef6e1b9795b35f4b87a0805b79edd4eb0931e35e517d7",
  "url": "https://osv.dev/vulnerability/CVE-2026-68464",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "mmc: sdhci-esdhc-imx: disable irq during suspend to fix unhandled interrupt",
    "summary": "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.",
    "evidence": "osv:CVE-2026-68464",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "6.18.40",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "7.1.5",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "unknown",
    "structured": {
      "id": "CVE-2026-68464",
      "aliases": [
        "CVE-2026-68464"
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "676a83855614635af3bf31ad3f8fec4031f81354"
                },
                {
                  "fixed": "4f96903e2fd228aa96013372402d650f6dbe5cb3"
                },
                {
                  "fixed": "9bf4ee05a1109d889de9151ee78bd80293923f70"
                },
                {
                  "fixed": "9d87eaf985cef9581b6ed99b461b38e8cd666480"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-68464.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.16.0"
                },
                {
                  "fixed": "6.18.40"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.19.0"
                },
                {
                  "fixed": "7.1.5"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-68464.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:46.051405889Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/4f96903e2fd228aa96013372402d650f6dbe5cb3",
        "https://git.kernel.org/stable/c/9bf4ee05a1109d889de9151ee78bd80293923f70",
        "https://git.kernel.org/stable/c/9d87eaf985cef9581b6ed99b461b38e8cd666480",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/68xxx/CVE-2026-68464.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2026-68464",
        "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
      ],
      "provider_metadata": {
        "cna_assigner": "Linux",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/68xxx/CVE-2026-68464.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-68464",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": null
  },
  "source_id": "core-osv",
  "document_id": 514329,
  "published_at": "2026-08-15T05:51:23.578+00:00"
}