CVE-2026-64248

MIPS: smp: report dying CPU to RCU in stop_this_cpu()

CVE-2026-64248 is fixed in 38 products on 1 platform, first by ALAS2023-2026-1969, released July 20, 2026. It is not reported as exploited. Patch Radar priority: Routine.

Routine
CVSS
5.5
Moderate
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.0016
4th percentile

In the Linux kernel, the following vulnerability has been resolved: MIPS: smp: report dying CPU to RCU in stop_this_cpu() smp_send_stop() parks all secondary CPUs in stop_this_cpu(). 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. Since commit 91840be8f710 ("irq_work: Fix use-after-free in irq_work_single() on PREEMPT_RT") however, irq_work_sync() calls synchronize_rcu() on architectures without an irq_work self-IPI, i.e. where arch_irq_work_has_interrupt() returns false. That is the asm-generic default used by MIPS. Any irq_work_sync() issued in the reboot/shutdown 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 was noticed on several Realtek MIPS switch SoCs (MIPS interAptiv) and came up during kernel bump downstream in OpenWrt from 6.18.33 to 6.18.34, after the backport of the patch to the 6.18 stable branch. The patch also has been backported all the way back to 6.1. 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. MIPS shuts down all CPUs here without going through the CPU-hotplug mechanism, so this report is not otherwise issued. Reporting a dying CPU to RCU outside the regular hotplug offline path is not unprecedented: arm64 does the same in cpu_die_early(). There it is an exception for a CPU that was coming online and is aborting bringup, rather than the default shutdown action as on MIPS.

Where it's fixed

ProductFixed inFixReleased
Linux
bpftool6.12 · amzn 2023 1:6.12.95-124.187.amzn2023 ALAS2023-2026-2014 Aug 3, 2026
bpftool6.12-debuginfo · amzn 2023 1:6.12.95-124.187.amzn2023 ALAS2023-2026-2014 Aug 3, 2026
bpftool6.18 · amzn 2023 1:6.18.38-73.137.amzn2023 ALAS2023-2026-1969 Jul 20, 2026
bpftool6.18-debuginfo · amzn 2023 1:6.18.38-73.137.amzn2023 ALAS2023-2026-1969 Jul 20, 2026
kernel-livepatch-6.12.95-124.187 · amzn 2023 1:1.0-0.amzn2023 ALAS2023-2026-2014 Aug 3, 2026
kernel-livepatch-6.18.38-73.137 · amzn 2023 1:1.0-0.amzn2023 ALAS2023-2026-1969 Jul 20, 2026
kernel6.12 · amzn 2023 1:6.12.95-124.187.amzn2023 ALAS2023-2026-2014 Aug 3, 2026
kernel6.12-debuginfo · amzn 2023 1:6.12.95-124.187.amzn2023 ALAS2023-2026-2014 Aug 3, 2026
kernel6.12-debuginfo-common-aarch64 · amzn 2023 1:6.12.95-124.187.amzn2023 ALAS2023-2026-2014 Aug 3, 2026
kernel6.12-debuginfo-common-x86_64 · amzn 2023 1:6.12.95-124.187.amzn2023 ALAS2023-2026-2014 Aug 3, 2026
kernel6.12-devel · amzn 2023 1:6.12.95-124.187.amzn2023 ALAS2023-2026-2014 Aug 3, 2026
kernel6.12-headers · amzn 2023 1:6.12.95-124.187.amzn2023 ALAS2023-2026-2014 Aug 3, 2026
kernel6.12-modules-extra · amzn 2023 1:6.12.95-124.187.amzn2023 ALAS2023-2026-2014 Aug 3, 2026
kernel6.12-modules-extra-common · amzn 2023 1:6.12.95-124.187.amzn2023 ALAS2023-2026-2014 Aug 3, 2026
kernel6.12-tools · amzn 2023 1:6.12.95-124.187.amzn2023 ALAS2023-2026-2014 Aug 3, 2026
kernel6.12-tools-debuginfo · amzn 2023 1:6.12.95-124.187.amzn2023 ALAS2023-2026-2014 Aug 3, 2026
kernel6.12-tools-devel · amzn 2023 1:6.12.95-124.187.amzn2023 ALAS2023-2026-2014 Aug 3, 2026
kernel6.18 · amzn 2023 1:6.18.38-73.137.amzn2023 ALAS2023-2026-1969 Jul 20, 2026
kernel6.18-debuginfo · amzn 2023 1:6.18.38-73.137.amzn2023 ALAS2023-2026-1969 Jul 20, 2026
kernel6.18-debuginfo-common-aarch64 · amzn 2023 1:6.18.38-73.137.amzn2023 ALAS2023-2026-1969 Jul 20, 2026
kernel6.18-debuginfo-common-x86_64 · amzn 2023 1:6.18.38-73.137.amzn2023 ALAS2023-2026-1969 Jul 20, 2026
kernel6.18-devel · amzn 2023 1:6.18.38-73.137.amzn2023 ALAS2023-2026-1969 Jul 20, 2026
kernel6.18-headers · amzn 2023 1:6.18.38-73.137.amzn2023 ALAS2023-2026-1969 Jul 20, 2026
kernel6.18-modules-extra · amzn 2023 1:6.18.38-73.137.amzn2023 ALAS2023-2026-1969 Jul 20, 2026
kernel6.18-modules-extra-common · amzn 2023 1:6.18.38-73.137.amzn2023 ALAS2023-2026-1969 Jul 20, 2026
kernel6.18-tools · amzn 2023 1:6.18.38-73.137.amzn2023 ALAS2023-2026-1969 Jul 20, 2026
kernel6.18-tools-debuginfo · amzn 2023 1:6.18.38-73.137.amzn2023 ALAS2023-2026-1969 Jul 20, 2026
kernel6.18-tools-devel · amzn 2023 1:6.18.38-73.137.amzn2023 ALAS2023-2026-1969 Jul 20, 2026
linux · Debian 12.15 (bookworm) 6.1.180-1 DEBIAN-CVE-2026-64248 Jul 25, 2026
linux · Debian 13.5 (trixie) 6.12.95-1 DEBIAN-CVE-2026-64248 Jul 25, 2026
linux · Debian 14 7.1.3-1 DEBIAN-CVE-2026-64248 Jul 25, 2026
microvm-kernel6.18 · amzn 2023 1:6.18.38-73.137.amzn2023 ALAS2023-2026-1969 Jul 20, 2026
perf6.12 · amzn 2023 1:6.12.95-124.187.amzn2023 ALAS2023-2026-2014 Aug 3, 2026
perf6.12-debuginfo · amzn 2023 1:6.12.95-124.187.amzn2023 ALAS2023-2026-2014 Aug 3, 2026
perf6.18 · amzn 2023 1:6.18.38-73.137.amzn2023 ALAS2023-2026-1969 Jul 20, 2026
perf6.18-debuginfo · amzn 2023 1:6.18.38-73.137.amzn2023 ALAS2023-2026-1969 Jul 20, 2026
python3-perf6.12 · amzn 2023 1:6.12.95-124.187.amzn2023 ALAS2023-2026-2014 Aug 3, 2026
python3-perf6.12-debuginfo · amzn 2023 1:6.12.95-124.187.amzn2023 ALAS2023-2026-2014 Aug 3, 2026
python3-perf6.18 · amzn 2023 1:6.18.38-73.137.amzn2023 ALAS2023-2026-1969 Jul 20, 2026
python3-perf6.18-debuginfo · amzn 2023 1:6.18.38-73.137.amzn2023 ALAS2023-2026-1969 Jul 20, 2026

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.