LoongArch: Report dying CPU to RCU in stop_this_cpu()
In the Linux kernel, the following vulnerability has been resolved: LoongArch: Report dying CPU to RCU in stop_this_cpu() This is a port of MIPS commit 9f3f3bdc6d9dac1 ("MIPS: smp: report dying CPU to RCU in stop_this_cpu()"). smp_send_stop() parks all secondary CPUs in stop_this_cpu(). And the function marks the CPU offline for the scheduler via set_cpu_online(false) but never informs RCU, so RCU keeps expecting a quiescent state from CPUs that are now spinning forever with interrupts disabled. As long as nothing waits for an RCU grace period after smp_send_stop() this is harmless, which is why it went unnoticed. However, since commit 91840be8f710370 ("irq_work: Fix use-after-free in irq_work_single() on PREEMPT_RT"), irq_work_sync() calls synchronize_rcu() on architectures without an irq_work self-IPI, i.e. where arch_irq_work_has_interrupt() returns false. Any irq_work_sync() issued in the reboot/shutdown/halt path after smp_send_stop() then blocks on a grace period that can never complete, hanging the reboot: WARNING: CPU: 0 PID: 15 at kernel/irq_work.c:144 irq_work_queue_on ... rcu: INFO: rcu_sched detected stalls on CPUs/tasks: rcu: Offline CPU 1 blocking current GP. rcu: Offline CPU 2 blocking current GP. rcu: Offline CPU 3 blocking current GP. This issue needs some hacks to reproduce, and it was not noticed on LoongArch because arch_irq_work_has_interrupt() usually returns true. Call rcutree_report_cpu_dead() once interrupts are disabled, mirroring the generic CPU-hot
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.1.178, 6.12.95, 6.18.38, 6.6.145, 7.1.3
- CVEs
- CVE-2026-64250
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 7 Nov 2026, 07:48 UTC · Revision 1
Source evidence
LoongArch: Report dying CPU to RCU in stop_this_cpu()
core-osv · Original sourcePublished 24 Jul 2026, 15:31 UTC
In the Linux kernel, the following vulnerability has been resolved: LoongArch: Report dying CPU to RCU in stop_this_cpu() This is a port of MIPS commit 9f3f3bdc6d9dac1 ("MIPS: smp: report dying CPU to RCU in stop_this_cpu()"). smp_send_stop() parks all secondary CPUs in stop_this_cpu(). And the function marks the CPU offline for the scheduler via set_cpu_online(false) but never informs RCU, so RCU keeps expecting a quiescent state from CPUs that are now spinning forever with interrupts disabled. As long as nothing waits for an RCU grace period after smp_send_stop() this is harmless, which is why it went unnoticed. However, since commit 91840be8f710370 ("irq_work: Fix use-after-free in irq_work_single() on PREEMPT_RT"), irq_work_sync() calls synchronize_rcu() on architectures without an irq_work self-IPI, i.e. where arch_irq_work_has_interrupt() returns false. Any irq_work_sync() issued in the reboot/shutdown/halt path after smp_send_stop() then blocks on a grace period that can never complete, hanging the reboot: WARNING: CPU: 0 PID: 15 at kernel/irq_work.c:144 irq_work_queue_on ... rcu: INFO: rcu_sched detected stalls on CPUs/tasks: rcu: Offline CPU 1 blocking current GP. rcu: Offline CPU 2 blocking current GP. rcu: Offline CPU 3 blocking current GP. This issue needs some hacks to reproduce, and it was not noticed on LoongArch because arch_irq_work_has_interrupt() usually returns true. Call rcutree_report_cpu_dead() once interrupts are disabled, mirroring the generic CPU-hot
osv:CVE-2026-64250
Kernel
Fixed versions: 6.1.178, 6.6.145, 6.12.95, 6.18.38, 7.1.3
Complete source record
{
"id": "709dfdc79bc76cad8100e459f0ef99be2630ad4e8313c2274c3a4d6eec11018f",
"url": "https://osv.dev/vulnerability/CVE-2026-64250",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "LoongArch: Report dying CPU to RCU in stop_this_cpu()",
"summary": "In the Linux kernel, the following vulnerability has been resolved: LoongArch: Report dying CPU to RCU in stop_this_cpu() This is a port of MIPS commit 9f3f3bdc6d9dac1 (\"MIPS: smp: report dying CPU to RCU in stop_this_cpu()\"). smp_send_stop() parks all secondary CPUs in stop_this_cpu(). And the function marks the CPU offline for the scheduler via set_cpu_online(false) but never informs RCU, so RCU keeps expecting a quiescent state from CPUs that are now spinning forever with interrupts disabled. As long as nothing waits for an RCU grace period after smp_send_stop() this is harmless, which is why it went unnoticed. However, since commit 91840be8f710370 (\"irq_work: Fix use-after-free in irq_work_single() on PREEMPT_RT\"), irq_work_sync() calls synchronize_rcu() on architectures without an irq_work self-IPI, i.e. where arch_irq_work_has_interrupt() returns false. Any irq_work_sync() issued in the reboot/shutdown/halt path after smp_send_stop() then blocks on a grace period that can never complete, hanging the reboot: WARNING: CPU: 0 PID: 15 at kernel/irq_work.c:144 irq_work_queue_on ... rcu: INFO: rcu_sched detected stalls on CPUs/tasks: rcu: Offline CPU 1 blocking current GP. rcu: Offline CPU 2 blocking current GP. rcu: Offline CPU 3 blocking current GP. This issue needs some hacks to reproduce, and it was not noticed on LoongArch because arch_irq_work_has_interrupt() usually returns true. Call rcutree_report_cpu_dead() once interrupts are disabled, mirroring the generic CPU-hot",
"evidence": "osv:CVE-2026-64250",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.1.178",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.145",
"evidence": "/affected/1/ranges"
},
{
"value": "6.12.95",
"evidence": "/affected/1/ranges"
},
{
"value": "6.18.38",
"evidence": "/affected/1/ranges"
},
{
"value": "7.1.3",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2026-64250",
"aliases": [
"CVE-2026-64250"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "2dc79362302922cb18f35e262712b5e58de65442"
},
{
"fixed": "262dadc619e69ebeb97affd334cd1078a9704e98"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "eef4f71b46a9929ac33e968538c9dd5d96a02460"
},
{
"fixed": "1fa22de588a65880d6fe54c38c87fffe7d519f60"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "684a78183c54c23e70d1cba320f7fc184604210b"
},
{
"fixed": "a0269e928728f970c782319fee53d92d4ea4e512"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "18c0456ea2615b1a743a6db739c74411c3b42bc6"
},
{
"fixed": "90e254f18b8c224460082329dd5c42fd30995c2f"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "91840be8f710370607f949a627e070896faeddb8"
},
{
"fixed": "0833b2b84c2fc1387f8165f0cbf6a02d67f647a5"
},
{
"fixed": "f2539c56c74691e7a88af6372ba2b48c06ed2fe4"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "6.1.175"
},
{
"fixed": "6.1.178"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "6.6.142"
},
{
"fixed": "6.6.145"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "6.12.92"
},
{
"fixed": "6.12.95"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "6.18.34"
},
{
"fixed": "6.18.38"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "7.0.11"
},
{
"fixed": "7.1"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "81b582784518196eff1050212a046bc29d3a05dd"
}
]
}
],
"versions": [
"v6.1.177",
"v6.1.176",
"v6.1.175",
"v6.6.144",
"v6.6.143",
"v6.6.142",
"v6.12.94",
"v6.12.93",
"v6.12.92",
"v6.18.37",
"v6.18.36",
"v6.18.35",
"v6.18.34",
"v7.0.14",
"v7.0.13",
"v7.0.12",
"v7.0.11"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-64250.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "6.1.178"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.145"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.12.95"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.18.38"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "7.1.3"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-64250.json"
}
}
],
"modified": "2026-10-28T02:30:50.602087034Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/0833b2b84c2fc1387f8165f0cbf6a02d67f647a5",
"https://git.kernel.org/stable/c/1fa22de588a65880d6fe54c38c87fffe7d519f60",
"https://git.kernel.org/stable/c/262dadc619e69ebeb97affd334cd1078a9704e98",
"https://git.kernel.org/stable/c/90e254f18b8c224460082329dd5c42fd30995c2f",
"https://git.kernel.org/stable/c/a0269e928728f970c782319fee53d92d4ea4e512",
"https://git.kernel.org/stable/c/f2539c56c74691e7a88af6372ba2b48c06ed2fe4",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/64xxx/CVE-2026-64250.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-64250",
"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/2026/64xxx/CVE-2026-64250.json"
}
},
"related_cves": [
{
"value": "CVE-2026-64250",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 518677,
"published_at": "2026-07-24T15:31:17.021+00:00"
}