https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 15:25:39 +0000 https://vulnerability.circl.lu/vuln/cve-2026-68464 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mmc: sdhci-esdhc-imx: disable irq during suspend to fix unhandled interrupt</p> <p>When using WIFI out-of-band wakeup, an &#34;irq xxx: nobody cared&#34; warning occurs. This happens because the usdhc interrupt is not disabled during system suspend when device_may_wakeup() returns false.</p> <p>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 &#34;nobody cared&#34; warning</p> <p>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.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mmc: sdhci-esdhc-imx: disable irq during suspend to fix unhandled interrupt</p> <p>When using WIFI out-of-band wakeup, an &#34;irq xxx: nobody cared&#34; warning occurs. This happens because the usdhc interrupt is not disabled during system suspend when device_may_wakeup() returns false.</p> <p>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 &#34;nobody cared&#34; warning</p> <p>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.</p> https://vulnerability.circl.lu/vuln/cve-2026-68464