CVE-2022-48921: sched/fair: Fix fault in reweight_entity
In the Linux kernel, the following vulnerability has been resolved:
sched/fair: Fix fault in reweight_entity
Syzbot found a GPF in reweight_entity. This has been bisected to
commit 4ef0c5c6b5ba ("kernel/sched: Fix sched_fork() access an invalid
sched_task_group")
There is a race between sched_post_fork() and setpriority(PRIO_PGRP)
within a thread group that causes a null-ptr-deref in
reweight_entity() in CFS. The scenario is that the main process spawns
number of new threads, which then call setpriority(PRIO_PGRP, 0, -20),
wait, and exit. For each of the new threads the copy_process() gets
invoked, which adds the new task_struct and calls sched_post_fork()
for it.
In the above scenario there is a possibility that
setpriority(PRIO_PGRP) and set_one_prio() will be called for a thread
in the group that is just being created by copy_process(), and for
which the sched_post_fork() has not been executed yet. This will
trigger a null pointer dereference in reweight_entity(), as it will
try to access the run queue pointer, which hasn't been set.
Before the mentioned change the cfs_rq pointer for the task has been
set in sched_fork(), which is called much earlier in copy_process(),
before the new task is added to the thread_group. Now it is done in
the sched_post_fork(), which is called after that. To fix the issue
the remove the update_load param from the update_load param() function
and call reweight_task() only if the task flag doesn't have the
TASK_NEW flag set.
Security readout for executives and security teams
Plain-English summary
This Linux kernel scheduler bug can crash the kernel when a thread group races process creation against priority changes. The sources describe a null pointer dereference, so the practical business risk is mainly service disruption on affected Linux hosts.
Executive priority
Treat as a patch-management priority for Linux availability risk, especially shared compute or externally managed workload platforms. It is not currently supported as an emergency internet-exposed issue by the supplied evidence.
Technical view
The flaw is in CFS reweight_entity(). A race between sched_post_fork() and setpriority(PRIO_PGRP) can reach reweight_entity() before the task runqueue pointer is initialized, causing a null pointer dereference. Kernel stable commits adjust reweight behavior for TASK_NEW tasks.
Likely exposure
Exposure appears limited to Linux systems running affected kernel versions or commits listed in the CVE record. The described trigger requires local process/thread activity and priority changes, not a remote network path.
Exploitation context
The CVE record says syzbot found the fault. KEV is false, and the supplied sources do not claim active exploitation, public exploit use, or remote exploitation.
Researcher notes
Evidence is limited to the CVE text and kernel stable references. The source describes a local scheduler race and syzbot discovery, but provides no CVSS, CWE, exploit maturity, distro-specific status, or confirmed impact beyond fault/null dereference.
Mitigation direction
Identify affected Linux kernel versions across servers, containers hosts, appliances, and embedded systems.
Apply vendor or distribution kernel updates that include the referenced stable fixes.
For custom kernels, confirm the relevant upstream stable commit is included.
Prioritize multi-tenant or untrusted-workload hosts because local users may influence scheduler paths.
Monitor vendor advisories because the source bundle provides no CVSS or operational workaround.
Validation and detection
Compare running kernel versions against affected versions and vendor security advisories.
Confirm patched kernels include one of the referenced stable fixes or equivalent backport.
Review kernel crash records for null pointer dereferences involving reweight_entity or scheduler code.
Check asset coverage for Linux hosts not managed by standard patch tooling.
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-48921 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.