Bug 2506809 (CVE-2026-64211) - CVE-2026-64211 kernel: srcu: Don't queue workqueue handlers to never-online CPUs
Summary: CVE-2026-64211 kernel: srcu: Don't queue workqueue handlers to never-online CPUs
Keywords:
Status: NEW
Alias: CVE-2026-64211
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-07-24 16:04 UTC by OSIDB Bzimport
Modified: 2026-07-28 11:36 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-07-24 16:04:56 UTC
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.

Comment 1 Mauro Matteo Cascella 2026-07-28 11:33:11 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2026072414-CVE-2026-64211-f6d4@gregkh/T


Note You need to log in before you can comment on or make changes to this bug.