CVE-2026-64250

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-hotplug offline path, so RCU stops waiting on the parked CPUs and grace periods can still complete. LoongArch shuts down all CPUs here without going through the CPU-hotplug mechanism, so this report is not otherwise issued.

• https://git.kernel.org/stable/c/0833b2b84c2fc1387f8165f0cbf6a02d67f647a5Patch
• https://git.kernel.org/stable/c/1fa22de588a65880d6fe54c38c87fffe7d519f60Patch
• https://git.kernel.org/stable/c/262dadc619e69ebeb97affd334cd1078a9704e98Patch
• https://git.kernel.org/stable/c/90e254f18b8c224460082329dd5c42fd30995c2fPatch
• https://git.kernel.org/stable/c/a0269e928728f970c782319fee53d92d4ea4e512Patch
• https://git.kernel.org/stable/c/f2539c56c74691e7a88af6372ba2b48c06ed2fe4Patch

Published

Jul 24, 2026

Last Modified

Aug 12, 2026

Status

Analyzed

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-64244In the Linux kernel, the following vulnerability has been re…
• CVE-2026-64245In the Linux kernel, the following vulnerability has been re…
• CVE-2026-64246In the Linux kernel, the following vulnerability has been re…
• CVE-2026-64247In the Linux kernel, the following vulnerability has been re…8.4
• CVE-2026-64248In the Linux kernel, the following vulnerability has been re…
• CVE-2026-64249In the Linux kernel, the following vulnerability has been re…
• CVE-2026-64251In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-64252In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2026-64253In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2026-64254In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2026-64255In the Linux kernel, the following vulnerability has been re…8.8
• CVE-2026-64256In the Linux kernel, the following vulnerability has been re…5.5