mmc: sdhci-esdhc-imx: disable irq during suspend to fix unhandled interrupt
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.18.407.1.57.2In 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.
From the CVE record · Linux
The Linux kernel’s sdhci-esdhc-imx driver can leave the usdhc interrupt enabled during system suspend when device_may_wakeup() is false. If Wi-Fi out-of-band wakeup occurs, a card interrupt can arrive before usdhc has resumed, causing an unhandled interrupt warning. The input does not describe an attacker-controlled trigger or any authentication or user-interaction requirements.
Engineers running Linux systems that use the sdhci-esdhc-imx driver and Wi-Fi out-of-band wakeup should check their kernel; affected versions are not specified.