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 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 ]
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 5.10.224, 5.15.165, 5.4.282, 6.1.103, 6.10.3, 6.6.44
- CVEs
- CVE-2024-42290
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 06:58 UTC · Revision 1
Source evidence
irqchip/imx-irqsteer: Handle runtime power management correctly
core-osv · Original sourcePublished 17 Aug 2024, 09:08 UTC
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 ]
osv:CVE-2024-42290
Kernel
Fixed versions: 5.4.282, 5.10.224, 5.15.165, 6.1.103, 6.6.44, 6.10.3
Complete source record
{
"id": "e3811da4fc1bd1c92faf8a5876643c6cc59f08c354643188fb3df96c055134ec",
"url": "https://osv.dev/vulnerability/CVE-2024-42290",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "irqchip/imx-irqsteer: Handle runtime power management correctly",
"summary": "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 ]",
"evidence": "osv:CVE-2024-42290",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "5.4.282",
"evidence": "/affected/1/ranges"
},
{
"value": "5.10.224",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.165",
"evidence": "/affected/1/ranges"
},
{
"value": "6.1.103",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.44",
"evidence": "/affected/1/ranges"
},
{
"value": "6.10.3",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2024-42290",
"aliases": [
"CVE-2024-42290"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "0136afa08967f6e160b9b4e85a7a70e4180a8333"
},
{
"fixed": "a590e8dea3df2639921f874d763be961dd74e8f9"
},
{
"fixed": "3a2884a44e5cda192df1b28e9925661f79f599a1"
},
{
"fixed": "fa1803401e1c360efe6342fb41d161cc51748a11"
},
{
"fixed": "58c56735facb225a5c46fa4b8bbbe7f31d1cb894"
},
{
"fixed": "21bd3f9e7f924cd2fc892a484e7a50c7e1847565"
},
{
"fixed": "f8ae38f1dfe652779c7c613facbc257cec00ac44"
},
{
"fixed": "33b1c47d1fc0b5f06a393bb915db85baacba18ea"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-42290.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.0.0"
},
{
"fixed": "5.4.282"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.5.0"
},
{
"fixed": "5.10.224"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.165"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.103"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.44"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.10.3"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-42290.json"
}
}
],
"modified": "2026-10-28T02:30:26.859383862Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/21bd3f9e7f924cd2fc892a484e7a50c7e1847565",
"https://git.kernel.org/stable/c/33b1c47d1fc0b5f06a393bb915db85baacba18ea",
"https://git.kernel.org/stable/c/3a2884a44e5cda192df1b28e9925661f79f599a1",
"https://git.kernel.org/stable/c/58c56735facb225a5c46fa4b8bbbe7f31d1cb894",
"https://git.kernel.org/stable/c/a590e8dea3df2639921f874d763be961dd74e8f9",
"https://git.kernel.org/stable/c/f8ae38f1dfe652779c7c613facbc257cec00ac44",
"https://git.kernel.org/stable/c/fa1803401e1c360efe6342fb41d161cc51748a11",
"https://lists.debian.org/debian-lts-announce/2024/10/msg00003.html",
"https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/42xxx/CVE-2024-42290.json",
"https://nvd.nist.gov/vuln/detail/CVE-2024-42290",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/42xxx/CVE-2024-42290.json"
}
},
"related_cves": [
{
"value": "CVE-2024-42290",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 493188,
"published_at": "2024-08-17T09:08:59.848+00:00"
}