CVE-2022-50100: sched/core: Do not requeue task on CPU excluded from cpus_mask
In the Linux kernel, the following vulnerability has been resolved:
sched/core: Do not requeue task on CPU excluded from cpus_mask
The following warning was triggered on a large machine early in boot on
a distribution kernel but the same problem should also affect mainline.
WARNING: CPU: 439 PID: 10 at ../kernel/workqueue.c:2231 process_one_work+0x4d/0x440
Call Trace:
<TASK>
rescuer_thread+0x1f6/0x360
kthread+0x156/0x180
ret_from_fork+0x22/0x30
</TASK>
Commit c6e7bd7afaeb ("sched/core: Optimize ttwu() spinning on p->on_cpu")
optimises ttwu by queueing a task that is descheduling on the wakelist,
but does not check if the task descheduling is still allowed to run on that CPU.
In this warning, the problematic task is a workqueue rescue thread which
checks if the rescue is for a per-cpu workqueue and running on the wrong CPU.
While this is early in boot and it should be possible to create workers,
the rescue thread may still used if the MAYDAY_INITIAL_TIMEOUT is reached
or MAYDAY_INTERVAL and on a sufficiently large machine, the rescue
thread is being used frequently.
Tracing confirmed that the task should have migrated properly using the
stopper thread to handle the migration. However, a parallel wakeup from udev
running on another CPU that does not share CPU cache observes p->on_cpu and
uses task_cpu(p), queues the task on the old CPU and triggers the warning.
Check that the wakee task that is descheduling is still allowed to run
on its current CPU and if not, wait for the descheduling to complete
and select an allowed CPU.
Security readout for executives and security teams
Plain-English summary
This Linux kernel scheduler issue can place a waking task back onto a CPU it is no longer allowed to run on. The source describes kernel warnings during early boot on very large systems, not data theft or remote compromise. Severity and practical impact are not quantified in the provided sources.
Executive priority
Track this as a kernel maintenance item, not an emergency remote-exploitation event based on current evidence. Prioritize patch planning for large Linux servers and platforms where early-boot reliability or scheduler correctness matters operationally.
Technical view
The bug follows commit c6e7bd7afaeb, where ttwu() can queue a descheduling task on its old CPU without confirming that CPU remains in the task's cpus_mask. A parallel wakeup can race migration and trigger incorrect CPU placement, observed with workqueue rescue threads on large machines.
Likely exposure
Exposure is most relevant to Linux systems running affected kernel builds derived from the listed scheduler change, especially large multi-CPU systems. The bundle lists Linux kernel versions including 5.8, 5.15.61, 5.18.18, 5.19.2, and 6.0, but distribution-specific status must be confirmed.
Exploitation context
The provided sources do not report active exploitation, and KEV status is false. The described trigger is a scheduler race involving CPU affinity and wakeups, observed early in boot. No public exploit behavior, attacker prerequisites, or security impact class is established in the bundle.
Researcher notes
The evidence supports a Linux scheduler race condition fixed upstream, but not a full impact assessment. The source does not provide CVSS, CWE, exploitability, or distribution package mapping. Researchers should focus on affected kernel lineage and vendor backport confirmation.
Mitigation direction
Check your Linux distribution advisory for CVE-2022-50100 status and fixed kernel packages.
Update to a vendor-supported kernel containing the referenced upstream stable scheduler fix.
Prioritize large multi-CPU systems if they run affected kernel lines.
Avoid inventing local workarounds unless your Linux vendor documents them.
Validation and detection
Inventory running kernel versions across Linux hosts and appliances.
Compare installed kernels with vendor advisories for CVE-2022-50100.
Review boot logs for scheduler or workqueue warnings matching the described failure mode.
Confirm patched systems include one of the referenced stable fixes or vendor backport.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2022-50100 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
5Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Jun 18, 2025, 11:02 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.