CVE-2024-42290: Vulnerability in Linux Linux
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 ]
AI Analysis
Technical Summary
CVE-2024-42290 is a vulnerability identified in the Linux kernel specifically affecting the irqchip/imx-irqsteer driver, which is responsible for interrupt steering on certain i.MX platforms such as i.MX8QM and i.MX8QXP. The root cause of the vulnerability lies in improper handling of runtime power management during device probing. The power domain activation is triggered automatically via clk_prepare(), but on affected platforms, the power-on sequence invokes sleeping functions within an atomic context. This leads to a 'scheduling while atomic' bug, which is a kernel defect where the scheduler is invoked while interrupts or preemption are disabled, causing kernel warnings or potential deadlocks. The call trace provided shows that the issue occurs during the resume phase of runtime power management, involving mutex locks and clock preparation functions that are not safe to execute in atomic context. The vulnerability is addressed by implementing irq_bus_lock and sync_unlock interrupt chip callbacks to handle power management operations outside atomic contexts, ensuring that sleeping functions are not called while atomic. This fix prevents the kernel from entering an unstable state during device probing and runtime resume operations on affected hardware. There are no known exploits in the wild at this time, and no CVSS score has been assigned yet. The vulnerability is specific to Linux kernel versions containing the affected irqsteer driver code and impacts embedded or specialized systems using i.MX8QM and i.MX8QXP SoCs running Linux kernels with this irqsteer implementation.
Potential Impact
For European organizations, the impact of CVE-2024-42290 primarily concerns those deploying embedded Linux systems or industrial devices based on i.MX8QM and i.MX8QXP platforms. These platforms are commonly used in automotive, industrial automation, IoT gateways, and telecommunications equipment. The vulnerability can cause kernel instability, including kernel panics or deadlocks, leading to denial of service conditions on affected devices. This could disrupt critical infrastructure operations, manufacturing processes, or network equipment functionality. While the vulnerability does not directly enable privilege escalation or remote code execution, the resulting system instability can be exploited by attackers with local access to cause service interruptions. European sectors reliant on embedded Linux in critical systems—such as automotive suppliers, industrial control system operators, and telecom providers—may face operational risks if devices are not patched. Additionally, the complexity of the bug and its occurrence during power management routines could complicate troubleshooting and prolong downtime. However, since exploitation requires specific hardware platforms and local conditions, the threat is more targeted and less likely to affect general-purpose Linux servers or desktops.
Mitigation Recommendations
European organizations should prioritize updating Linux kernel versions on affected embedded devices to incorporate the patch that implements irq_bus_lock and sync_unlock callbacks for proper power management handling. Device manufacturers and integrators using i.MX8QM and i.MX8QXP platforms must verify that their kernel builds include this fix. For systems where immediate patching is not feasible, organizations should implement strict access controls to limit local user privileges and prevent untrusted code execution on affected devices. Monitoring kernel logs for 'scheduling while atomic' warnings can help detect attempts to trigger the bug. Additionally, organizations should engage with hardware vendors to obtain firmware and kernel updates and validate these in test environments before deployment. Given the embedded nature of the vulnerability, maintaining an inventory of devices using affected SoCs and Linux kernel versions is critical for targeted remediation. Finally, applying runtime integrity monitoring and anomaly detection on embedded devices can help identify abnormal kernel behavior indicative of exploitation attempts.
Affected Countries
Germany, France, Italy, Spain, United Kingdom, Netherlands, Sweden, Finland
CVE-2024-42290: Vulnerability in Linux Linux
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 ]
AI-Powered Analysis
Technical Analysis
CVE-2024-42290 is a vulnerability identified in the Linux kernel specifically affecting the irqchip/imx-irqsteer driver, which is responsible for interrupt steering on certain i.MX platforms such as i.MX8QM and i.MX8QXP. The root cause of the vulnerability lies in improper handling of runtime power management during device probing. The power domain activation is triggered automatically via clk_prepare(), but on affected platforms, the power-on sequence invokes sleeping functions within an atomic context. This leads to a 'scheduling while atomic' bug, which is a kernel defect where the scheduler is invoked while interrupts or preemption are disabled, causing kernel warnings or potential deadlocks. The call trace provided shows that the issue occurs during the resume phase of runtime power management, involving mutex locks and clock preparation functions that are not safe to execute in atomic context. The vulnerability is addressed by implementing irq_bus_lock and sync_unlock interrupt chip callbacks to handle power management operations outside atomic contexts, ensuring that sleeping functions are not called while atomic. This fix prevents the kernel from entering an unstable state during device probing and runtime resume operations on affected hardware. There are no known exploits in the wild at this time, and no CVSS score has been assigned yet. The vulnerability is specific to Linux kernel versions containing the affected irqsteer driver code and impacts embedded or specialized systems using i.MX8QM and i.MX8QXP SoCs running Linux kernels with this irqsteer implementation.
Potential Impact
For European organizations, the impact of CVE-2024-42290 primarily concerns those deploying embedded Linux systems or industrial devices based on i.MX8QM and i.MX8QXP platforms. These platforms are commonly used in automotive, industrial automation, IoT gateways, and telecommunications equipment. The vulnerability can cause kernel instability, including kernel panics or deadlocks, leading to denial of service conditions on affected devices. This could disrupt critical infrastructure operations, manufacturing processes, or network equipment functionality. While the vulnerability does not directly enable privilege escalation or remote code execution, the resulting system instability can be exploited by attackers with local access to cause service interruptions. European sectors reliant on embedded Linux in critical systems—such as automotive suppliers, industrial control system operators, and telecom providers—may face operational risks if devices are not patched. Additionally, the complexity of the bug and its occurrence during power management routines could complicate troubleshooting and prolong downtime. However, since exploitation requires specific hardware platforms and local conditions, the threat is more targeted and less likely to affect general-purpose Linux servers or desktops.
Mitigation Recommendations
European organizations should prioritize updating Linux kernel versions on affected embedded devices to incorporate the patch that implements irq_bus_lock and sync_unlock callbacks for proper power management handling. Device manufacturers and integrators using i.MX8QM and i.MX8QXP platforms must verify that their kernel builds include this fix. For systems where immediate patching is not feasible, organizations should implement strict access controls to limit local user privileges and prevent untrusted code execution on affected devices. Monitoring kernel logs for 'scheduling while atomic' warnings can help detect attempts to trigger the bug. Additionally, organizations should engage with hardware vendors to obtain firmware and kernel updates and validate these in test environments before deployment. Given the embedded nature of the vulnerability, maintaining an inventory of devices using affected SoCs and Linux kernel versions is critical for targeted remediation. Finally, applying runtime integrity monitoring and anomaly detection on embedded devices can help identify abnormal kernel behavior indicative of exploitation attempts.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Linux
- Date Reserved
- 2024-07-30T07:40:12.268Z
- Cisa Enriched
- true
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 682d9828c4522896dcbe1e44
Added to database: 5/21/2025, 9:08:56 AM
Last enriched: 6/29/2025, 6:55:08 AM
Last updated: 8/16/2025, 9:35:38 PM
Views: 10
Related Threats
CVE-2025-53948: CWE-415 Double Free in Santesoft Sante PACS Server
HighCVE-2025-52584: CWE-122 Heap-based Buffer Overflow in Ashlar-Vellum Cobalt
HighCVE-2025-46269: CWE-122 Heap-based Buffer Overflow in Ashlar-Vellum Cobalt
HighCVE-2025-54862: CWE-79 Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') in Santesoft Sante PACS Server
MediumCVE-2025-54759: CWE-79 Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') in Santesoft Sante PACS Server
MediumActions
Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.