CVE-2026-64211

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.

Package Linux Kernel
Published 2026-07-24
Last modified 2026-07-24
Patch available
Yes

Affected versions

Linux kernel versions 7.0 and later are affected. Fixed in 7.0.11, 7.1 and their respective stable series.

Affected from
≥ 7.0
Fixed in
✓ 7.0.11 7.0.x ✓ 7.1

Frequently asked questions

  • What is CVE-2026-64211?

    CVE-2026-64211 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 7.0 onward and has been patched in 7.0.11 and 7.1. CVE-2026-64211 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

  • Is there a patch available for CVE-2026-64211?

    Yes. CVE-2026-64211 has been patched. Fixed versions include 7.0.11 and 7.1. If you are running Linux kernel 7.0 or later up to the fix versions, apply the relevant patch for your kernel branch.

  • Is CVE-2026-64211 actively exploited?

    No. CVE-2026-64211 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.