Read the docs
TI-2026-45812 Aliases CVE-2026-64248GHSA-63rm-9p6r-635w

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

Priority LOW 24Published · Updated

Key facts

Attack vector
Local
Privileges required
Low
User interaction
None
Attack complexity
Low
Impact type
—
Confidentiality · integrity · availability
None · None · High
Fix status
Fixed

Attack profile from CVSS 3.1 · NVD. Fix status from CNA.

Summary

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.

Why it matters now

EPSS 0.00158 4th percentileScored 2026-11-07
Fix Fixed Linux (Linux): 6.1.178, 6.6.145, 6.12.95 +4

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
LinuxLinux6.1.175 to before 6.1.178; 6.6.142 to before 6.6.145; 6.12.92 to before 6.12.95; 6.18.34 to before 6.18.38; 7.0.11 to before 7.16.1.178, 6.6.145, 6.12.95, 6.18.38, 7.1Patch availableCNA
LinuxLinux7.1 and later6.1.178, 6.6.145, 6.12.95, 6.18.38, 7.1.3, 7.2Patch availableCNA
  • Linux VendorLinux Affected 6.1.175 to before 6.1.178; 6.6.142 to before 6.6.145; 6.12.92 to before 6.12.95; 6.18.34 to before 6.18.38; 7.0.11 to before 7.1 Fixed in 6.1.178, 6.6.145, 6.12.95, 6.18.38, 7.1 Patch available CNA
  • Linux VendorLinux Affected 7.1 and later Fixed in 6.1.178, 6.6.145, 6.12.95, 6.18.38, 7.1.3, 7.2 Patch available CNA

CPE configurations NVD · 6

CPEVersionsRoleVendor
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*6.1.175 to before 6.1.178; 6.6.142 to before 6.6.145; 6.12.92 to before 6.12.95; 6.18.34 to before 6.18.38; 7.0.11 to before 7.1; 7.1.1 to before 7.1.3VulnerableLinux
cpe:2.3:o:linux:linux_kernel:7.1:-:*:*:*:*:*:*7.1VulnerableLinux
cpe:2.3:o:linux:linux_kernel:7.1:rc4:*:*:*:*:*:*7.1 rc4VulnerableLinux
cpe:2.3:o:linux:linux_kernel:7.1:rc5:*:*:*:*:*:*7.1 rc5VulnerableLinux
cpe:2.3:o:linux:linux_kernel:7.1:rc6:*:*:*:*:*:*7.1 rc6VulnerableLinux
cpe:2.3:o:linux:linux_kernel:7.1:rc7:*:*:*:*:*:*7.1 rc7VulnerableLinux
  • cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* Versions 6.1.175 to before 6.1.178; 6.6.142 to before 6.6.145; 6.12.92 to before 6.12.95; 6.18.34 to before 6.18.38; 7.0.11 to before 7.1; 7.1.1 to before 7.1.3 Vulnerable ·Linux
  • cpe:2.3:o:linux:linux_kernel:7.1:-:*:*:*:*:*:* Versions 7.1 Vulnerable ·Linux
  • cpe:2.3:o:linux:linux_kernel:7.1:rc4:*:*:*:*:*:* Versions 7.1 rc4 Vulnerable ·Linux
  • cpe:2.3:o:linux:linux_kernel:7.1:rc5:*:*:*:*:*:* Versions 7.1 rc5 Vulnerable ·Linux
  • cpe:2.3:o:linux:linux_kernel:7.1:rc6:*:*:*:*:*:* Versions 7.1 rc6 Vulnerable ·Linux
  • cpe:2.3:o:linux:linux_kernel:7.1:rc7:*:*:*:*:*:* Versions 7.1 rc7 Vulnerable ·Linux

Remediation

  • Fix · CNA Linux (Linux) Fixed in 6.1.178, 6.6.145, 6.12.95, 6.18.38, 7.1
  • Fix · CNA Linux (Linux) Fixed in 6.1.178, 6.6.145, 6.12.95, 6.18.38, 7.1.3, 7.2

Vendor assessments

Red Hat

Red Hat rating: Low. Red Hat's page for this CVE →

Not affected: 5 products
  • Red Hat Enterprise Linux 10
  • Red Hat Enterprise Linux 6
  • Red Hat Enterprise Linux 7
  • Red Hat Enterprise Linux 8
  • Red Hat Enterprise Linux 9

Timeline

  1. 2026-10-02 Threatist record created from CVE-2026-64248
  2. 2026-10-03 Alias added: GHSA-63rm-9p6r-635w
  3. 2026-10-20 Affected versions changed · Red Hat

References

  • TI-2025-26358 tls: fix handling of zero-length records on the rx_list KEVCVSS 3.1CRITICAL 9.8
  • TI-2026-38352 netfilter: bridge: make ebt_snat ARP rewrite writable KEVCVSS 3.1HIGH 8.8
  • TI-2013-05264 The (1) get_user and (2) put_user API functions in the Linux kernel before 3.5.5 on the… KEVCVSS 3.1HIGH 8.8
  • TI-2022-00125 Integer overflow in kernel KEVCVSS 3.1HIGH 8.4
  • TI-2013-01864 The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9… KEVCVSS 3.1HIGH 8.4
  • TI-2021-05514 Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACE KEVCVSS 3.1HIGH 8.3
See all 15278 →

Sources