CVE-2026-64211
Last modified
CVE-2026-64211 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: srcu: Don't queue workqueue handlers to never-online CPUs While an srcu_struct structure is in the midst of switching from CPU-0 to all-CPUs state, it can attempt to invoke callbacks for CPUs that have never been online. Worse yet, it can attempt in invoke callbacks for CPUs that never will be online, even including imaginary CPUs not in cpu_possible_mask. EPSS estimates a 0.15% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: srcu: Don't queue workqueue handlers to never-online CPUs While an srcu_struct structure is in the midst of switching from CPU-0 to all-CPUs state, it can attempt to invoke callbacks for CPUs that have never been online. Worse yet, it can attempt in invoke callbacks for CPUs that never will be online, even including imaginary CPUs not in cpu_possible_mask. This can cause hangs on s390, which is not set up to deal with workqueue handlers being scheduled on such CPUs. This commit therefore causes Tree SRCU to refrain from queueing workqueue handlers on CPUs that have not yet (and might never) come online. Because callbacks are not invoked on CPUs that have not been online, it is an error to invoke call_srcu(), synchronize_srcu(), or synchronize_srcu_expedited() on a CPU that is not yet fully online. However, it turns out to be less code to redirect the callbacks from too-early invocations of call_srcu() than to warn about such invocations. This commit therefore also redirects callbacks queued on not-yet-fully-online CPUs to the boot CPU.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 7.0.1, < 7.0.11 | — |
| Linux | Linux Kernel | 7.0 | — |
| Linux | Linux Kernel | 7.1 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-64211?
How severe is CVE-2026-64211?
How do I fix CVE-2026-64211?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-64206In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-64207In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64208In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-64209In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-6421A vulnerability has been found in Mobatek MobaXterm Home Edi…7
- CVE-2026-64210In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-64212In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64213In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64214In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64215In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64216In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-64217In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2026-64211?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
