Menu

Star on GitHub · 3.2k

CVE-2026-64250

5.5 · MEDIUM

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 C…

Published Jul 24, 2026EPSS 0.16%

Overview

CVE-2026-64250 is a medium-severity vulnerability. It was published on July 24, 2026 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical 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 neve

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-64250?

CVE-2026-64250 is a medium-severity vulnerability. It was published on July 24, 2026 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

How severe is CVE-2026-64250?

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-64250?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-64250?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-64250 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related MEDIUM CVEs from 2026

View all