CVE-2024-42290: irqchip/imx-irqsteer: Handle runtime power management correctly
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 clkprepare(). 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: schedulebug+0x54/0x6c schedule+0x7f0/0xa94 schedule+0x5c/0xc4 schedulepreemptdisabled+0x24/0x40 mutexlock.constprop.0+0x2c0/0x540 mutexlockslowpath+0x14/0x20 mutexlock+0x48/0x54 clkpreparelock+0x44/0xa0 clkprepare+0x20/0x44 imxirqsteerresume+0x28/0xe0 pmgenericruntimeresume+0x2c/0x44 genpdruntimeresume+0x30/0x80 genpdruntimeresume+0xc8/0x2c0 rpmcallback+0x48/0x1d8 rpmcallback+0x6c/0x78 rpmresume+0x490/0x6b4 pmruntimeresume+0x50/0x94 irqchippmget+0x2c/0xa0 irqdosethandler+0x178/0x24c irqsetchainedhandleranddata+0x60/0xa4 mxcgpioprobe+0x160/0x4b0
Cure this by implementing the irqbuslock/syncunlock() 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 Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-42290?
CVE-2024-42290 has been classified with a significant severity level due to its impact on runtime power management in the Linux kernel.
How do I fix CVE-2024-42290?
To fix CVE-2024-42290, update your Linux kernel to versions 5.10.226-1, 6.1.123-1, 6.1.119-1, 6.12.11-1, 6.12.12-1 or the patched version of linux-6.1.
Which software versions are affected by CVE-2024-42290?
CVE-2024-42290 affects Linux kernel versions up to and including 5.10.223-1 and its derivatives.
What platforms are affected by CVE-2024-42290?
CVE-2024-42290 specifically affects platforms like i.MX8QM and i.MX8QXP.
Is there a known exploit for CVE-2024-42290?
As of now, there are no publicly disclosed exploits for CVE-2024-42290, but it is advisable to patch the vulnerability promptly.