CVE-2026-64250: LoongArch: Report dying CPU to RCU in stop_this_cpu()

mediumCVSS 5.5CVE-2026-64250

CSIRTS triage

product: LoongArchOther

What: Dying CPU needs to be reported to RCU in stop_this_cpu() to ensure proper handling.
Who is affected: Deployments using LoongArch architecture are affected.
Urgency: Remediation urgency is unknown as the severity is not specified.
Action: Monitor for updates regarding this issue.

AI-assisted analysis generated from the source advisory — verify against the original.

⚡ Watch LoongArch

Get an email when a new LoongArch advisory drops — max one per day, one-click unsubscribe.

Details

Source: Microsoft Security Response Center (INTL · vendor-psirt · site)
Severity: medium — CVSS 5.5
Published: 2026-07-14
Exploitation: Not in CISA KEV at last sync

Original advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-64250

Exploitation outlook

EPSS (FIRST.org) estimates each CVE’s probability of exploitation in the next 30 days — here is the CSIRTS.com read on those numbers.

Low exploitation riskCVE-2026-642500.16% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 6% of all scored CVEs.

Referenced CVEs

CVE	CSIRTS overview	External
CVE-2026-64250	coverage & exploitation status	NVD · CVE.org

Same CVEs, other sources

How other CERTs, PSIRTs and databases cover the vulnerabilities in this advisory.

Recent advisories for LoongArch

A cluster of recent advisories against the same product widens the attack surface — attackers routinely chain freshly published CVEs on one product, so review these together.

unknownCVE-2026-64250: In the Linux kernel, the following vulnerability has been resolved: LoongArch: Report dying CP…nvd · 2026-07-24