Description
In the Linux kernel, the following vulnerability has been resolved: irqchip/imx-irqsteer: Handle runtime power management correctly The power domain is automatically activated from clk_prepare(). However, on certain platforms like i.MX8QM and i.MX8QXP, the power-on handling invokes sleeping functions, which triggers the 'scheduling while atomic' bug in the context switch path during device probing: BUG: scheduling while atomic: kworker/u13:1/48/0x00000002 Call trace: __schedule_bug+0x54/0x6c __schedule+0x7f0/0xa94 schedule+0x5c/0xc4 schedule_preempt_disabled+0x24/0x40 __mutex_lock.constprop.0+0x2c0/0x540 __mutex_lock_slowpath+0x14/0x20 mutex_lock+0x48/0x54 clk_prepare_lock+0x44/0xa0 clk_prepare+0x20/0x44 imx_irqsteer_resume+0x28/0xe0 pm_generic_runtime_resume+0x2c/0x44 __genpd_runtime_resume+0x30/0x80 genpd_runtime_resume+0xc8/0x2c0 __rpm_callback+0x48/0x1d8 rpm_callback+0x6c/0x78 rpm_resume+0x490/0x6b4 __pm_runtime_resume+0x50/0x94 irq_chip_pm_get+0x2c/0xa0 __irq_do_set_handler+0x178/0x24c irq_set_chained_handler_and_data+0x60/0xa4 mxc_gpio_probe+0x160/0x4b0 Cure this by implementing the irq_bus_lock/sync_unlock() interrupt chip callbacks and handle power management in them as they are invoked from non-atomic context. [ tglx: Rewrote change log, added Fixes tag ]
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Linux Linux
Default version status: unaffected
0136afa08967f6e160b9b4e85a7a70e4180a8333 to < a590e8dea3df2639921f874d763be961dd74e8f9affected0136afa08967f6e160b9b4e85a7a70e4180a8333 to < 3a2884a44e5cda192df1b28e9925661f79f599a1affected0136afa08967f6e160b9b4e85a7a70e4180a8333 to < fa1803401e1c360efe6342fb41d161cc51748a11affected0136afa08967f6e160b9b4e85a7a70e4180a8333 to < 58c56735facb225a5c46fa4b8bbbe7f31d1cb894affected0136afa08967f6e160b9b4e85a7a70e4180a8333 to < 21bd3f9e7f924cd2fc892a484e7a50c7e1847565affected0136afa08967f6e160b9b4e85a7a70e4180a8333 to < f8ae38f1dfe652779c7c613facbc257cec00ac44affected0136afa08967f6e160b9b4e85a7a70e4180a8333 to < 33b1c47d1fc0b5f06a393bb915db85baacba18eaaffected
Linux Linux
Default version status: affected
5.0affected0 to < 5.0unaffected5.4.282 to ≤ 5.4.*unaffected5.10.224 to ≤ 5.10.*unaffected5.15.165 to ≤ 5.15.*unaffected6.1.103 to ≤ 6.1.*unaffected6.6.44 to ≤ 6.6.*unaffected6.10.3 to ≤ 6.10.*unaffected6.11 to ≤ *unaffected
References
- https://git.kernel.org/stable/c/a590e8dea3df2639921f874d763be961dd74e8f9 ↗
- https://git.kernel.org/stable/c/3a2884a44e5cda192df1b28e9925661f79f599a1 ↗
- https://git.kernel.org/stable/c/fa1803401e1c360efe6342fb41d161cc51748a11 ↗
- https://git.kernel.org/stable/c/58c56735facb225a5c46fa4b8bbbe7f31d1cb894 ↗
- https://git.kernel.org/stable/c/21bd3f9e7f924cd2fc892a484e7a50c7e1847565 ↗
- https://git.kernel.org/stable/c/f8ae38f1dfe652779c7c613facbc257cec00ac44 ↗
- https://git.kernel.org/stable/c/33b1c47d1fc0b5f06a393bb915db85baacba18ea ↗
- https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html ↗
- https://lists.debian.org/debian-lts-announce/2024/10/msg00003.html ↗