CVE-2026-64250: LoongArch: Report dying CPU to RCU in stop_this_cpu()
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.15% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0833b2b84c2fc1387f8165f0cbf6a02d67f647a5, 1fa22de588a65880d6fe54c38c87fffe7d519f60, 262dadc619e69ebeb97affd334cd1078a9704e98; azl3 kernel 6.6.144.1-1 on Azure Linux 3.0 6.6.145.2-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 0833b2b84c2fc1387f8165f0cbf6a02d67f647a5, 1fa22de588a65880d6fe54c38c87fffe7d519f60, 262dadc619e69ebeb97affd334cd1078a9704e98; azl3 kernel 6.6.144.1-1 on Azure Linux 3.0 6.6.145.2-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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 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 needs some hacks to reproduce, and it was not noticed on LoongArch because arch_irq_work_has_interrupt() usually returns true. 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. LoongArch shuts down all CPUs here without going through the CPU-hotplug mechanism, so this report is not otherwise issued.
- Published
- Jul 24, 2026
- Updated
- Nov 8, 2026
- EPSS
- 0.1% · 4th percentile
- CWE
- —
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 81b582784518196eff1050212a046bc29d3a05dd, 7.1affected
- 2dc79362302922cb18f35e262712b5e58de65442 and later · before 262dadc619e69ebeb97affd334cd1078a9704e98affected · git
- eef4f71b46a9929ac33e968538c9dd5d96a02460 and later · before 1fa22de588a65880d6fe54c38c87fffe7d519f60affected · git
- 684a78183c54c23e70d1cba320f7fc184604210b and later · before a0269e928728f970c782319fee53d92d4ea4e512affected · git
- 18c0456ea2615b1a743a6db739c74411c3b42bc6 and later · before 90e254f18b8c224460082329dd5c42fd30995c2faffected · git
- 91840be8f710370607f949a627e070896faeddb8 and later · before 0833b2b84c2fc1387f8165f0cbf6a02d67f647a5affected · git
- 91840be8f710370607f949a627e070896faeddb8 and later · before f2539c56c74691e7a88af6372ba2b48c06ed2fe4affected · git
- 6.1.175 and later · before 6.1.178affected · semver
- 6.6.142 and later · before 6.6.145affected · semver
- 6.12.92 and later · before 6.12.95affected · semver
Affected versions · NVD (7)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.1.175 and later · before 6.1.178
- linux linux kernel6.6.142 and later · before 6.6.145
- linux linux kernel6.12.92 and later · before 6.12.95
- linux linux kernel6.18.34 and later · before 6.18.38
- linux linux kernel7.0.11 and later · before 7.1
- linux linux kernel7.1.1 and later · before 7.1.3
- linux linux kernel7.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.95-1 | 6.12.95-1 |
| Debian:14 | linux | before 7.1.3-1 | 7.1.3-1 |
| openSUSE:Tumbleweed | kernel-source | before 7.1.7-1.1 | 7.1.7-1.1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-64248Jul 24, 2026 · MIPS: smp: report dying CPU to RCU in stop_this_cpu()22Monitor
- ← EarlierCVE-2026-64249Jul 24, 2026 · fpga: region: fix use-after-free in child_regions_with_firmware()31Monitor
- Later →CVE-2026-64251Jul 24, 2026 · pwrseq: core: fix use-after-free in pwrseq_debugfs_seq_next()31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0833b2b84c2fc1387f8165f0cbf6a02d67f647a5 | Vendor (CNA) |
| Linux Linux | 1fa22de588a65880d6fe54c38c87fffe7d519f60 | Vendor (CNA) |
| Linux Linux | 262dadc619e69ebeb97affd334cd1078a9704e98 | Vendor (CNA) |
| Linux Linux | 6.1.178 | Vendor (CNA) |
| Linux Linux | 6.12.95 | Vendor (CNA) |
| Linux Linux | 6.18.38 | Vendor (CNA) |
| Linux Linux | 6.6.145 | Vendor (CNA) |
| Linux Linux | 7.1 | Vendor (CNA) |
| Linux Linux | 90e254f18b8c224460082329dd5c42fd30995c2f | Vendor (CNA) |
| Linux Linux | a0269e928728f970c782319fee53d92d4ea4e512 | Vendor (CNA) |
| Linux Linux | f2539c56c74691e7a88af6372ba2b48c06ed2fe4 | Vendor (CNA) |
| azl3 kernel 6.6.144.1-1 on Azure Linux 3.0 | 6.6.145.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.180-1 · Debian:12 | Package registry (OSV) |
| opensuse:kernel-source | 7.1.7-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0636 · Jul 27, 2026(Linux Kernel Güvenlik Bildirimi)
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/1fa22de588a65880d6fe54c38c87fffe7d519f60
- git.kernel.org/stable/c/262dadc619e69ebeb97affd334cd1078a9704e98
- git.kernel.org/stable/c/90e254f18b8c224460082329dd5c42fd30995c2f
- git.kernel.org/stable/c/a0269e928728f970c782319fee53d92d4ea4e512
- git.kernel.org/stable/c/f2539c56c74691e7a88af6372ba2b48c06ed2fe4
Vendor advisories and official records. Exploit/PoC links are deliberately left out.