Skip to main content

Linux Kernel EUVDEUVD-2026-48657

| CVE-2026-64248 MEDIUM
2026-07-24 Linux GHSA-63rm-9p6r-635w
5.5
CVSS 3.1 · NVD
Share

Severity by source

NVD PRIMARY
5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
vuln.today AI
5.5 MEDIUM

Local trigger (reboot initiation) requires low privileges; only availability is impacted as the system hangs with no data exposed.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
SUSE
MEDIUM
qualitative

Primary rating from NVD.

CVSS VectorNVD

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

5
Analysis Generated
Aug 13, 2026 - 20:55 vuln.today
CVSS changed
Aug 13, 2026 - 18:37 NVD
5.5 (MEDIUM)
Patch available
Jul 24, 2026 - 17:48 EUVD
CVE Published
Jul 24, 2026 - 15:31 nvd
MEDIUM 5.5
CVE Published
Jul 24, 2026 - 15:31 cve.org
UNKNOWN (no severity yet)

DescriptionNVD

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.

AnalysisAI

MIPS SMP systems running affected Linux kernel versions hang indefinitely during reboot or shutdown due to a missing RCU subsystem notification in the stop_this_cpu() shutdown path. When smp_send_stop() parks secondary CPUs, it correctly removes them from the scheduler's view via set_cpu_online(false) but never calls rcutree_report_cpu_dead(), leaving RCU waiting for quiescent states that can never arrive. The defect became reliably triggered after commit 91840be8f710 was backported to stable branches starting with 6.18.34, causing irq_work_sync() to invoke synchronize_rcu() on MIPS systems that lack an irq_work self-IPI, with no public exploit identified at time of analysis.

Technical ContextAI

The vulnerability resides in the MIPS-specific SMP shutdown path of the Linux kernel (cpe:2.3:a:linux:linux:*:*:*:*:*:*:*:*). The standard CPU hotplug offline path calls both set_cpu_online(false) and rcutree_report_cpu_dead() to inform all relevant kernel subsystems that a CPU is gone. The MIPS smp_send_stop() / stop_this_cpu() fast-shutdown path only performs the former, leaving RCU unaware that the parked CPUs will never issue another quiescent state. The interaction that made this latent bug observable is commit 91840be8f710 ('irq_work: Fix use-after-free in irq_work_single() on PREEMPT_RT'), which causes irq_work_sync() to call synchronize_rcu() on any architecture where arch_irq_work_has_interrupt() returns false - the asm-generic default used by MIPS. Any irq_work_sync() call issued after smp_send_stop() in the reboot/shutdown path then blocks on a grace period that can never complete. Observed platforms include Realtek MIPS interAptiv switch SoCs as deployed in OpenWrt-based networking gear. No CWE is formally assigned, but the root cause is a missing state synchronization notification - a resource management omission in an architecture-specific code path that bypasses the generic hotplug mechanism.

RemediationAI

Update to a patched kernel version: Linux 6.1.178, 6.6.145, 6.12.95, 6.18.38, 7.1.3, or 7.2-rc1 - all incorporate the fix that adds a rcutree_report_cpu_dead() call after interrupts are disabled in stop_this_cpu(), mirroring the arm64 cpu_die_early() precedent. Upstream stable commits are available at https://git.kernel.org/stable/c/e1919d026706544cb6e7251ec06e908edd6f34ee (6.18 branch), https://git.kernel.org/stable/c/f8a1ef884013dc99f712d3eb75624c7cd3fd94f6 (6.12 branch), https://git.kernel.org/stable/c/9fef09df42df55ab819b285ea892e0fc1b95a9c4, https://git.kernel.org/stable/c/6eda71977ee11c222f8ad4cae4d18d50448e56f4, https://git.kernel.org/stable/c/f9b57a0015c241274651f4b36627f56b1b5a8651, and https://git.kernel.org/stable/c/9f3f3bdc6d9dac1a5a8262ee7ad0f2ff1527a7e7. OpenWrt operators should upgrade to distribution builds incorporating kernel 6.18.38 or later. No meaningful kernel-level workaround exists short of patching; a power-cycle is required to recover a hung system. The fix itself has no known side effects as it mirrors the well-established hotplug offline notification path.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
openSUSE Tumbleweed Fixed
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected

Share

EUVD-2026-48657 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy