CVE-2022-48944: sched: Fix yet more sched_fork() races
In the Linux kernel, the following vulnerability has been resolved:
sched: Fix yet more sched_fork() races
Where commit 4ef0c5c6b5ba ("kernel/sched: Fix sched_fork() access an
invalid sched_task_group") fixed a fork race vs cgroup, it opened up a
race vs syscalls by not placing the task on the runqueue before it
gets exposed through the pidhash.
Commit 13765de8148f ("sched/fair: Fix fault in reweight_entity") is
trying to fix a single instance of this, instead fix the whole class
of issues, effectively reverting this commit.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel scheduler race condition in process creation. A prior fix for a cgroup-related fork race exposed tasks too early, creating another race with syscalls. The public record does not provide CVSS, concrete impact, or exploitation evidence, so urgency depends on whether affected kernels are present.
Executive priority
Monitor and patch through normal kernel maintenance unless critical Linux hosts match affected builds. Escalate if a vendor rates the downstream package more severely or confirms exploitable impact.
Technical view
The issue concerns sched_fork() ordering: a task could be exposed through pidhash before being placed on the runqueue. The kernel record says this opened a class of races after commit 4ef0c5c6b5ba and superseded a narrower reweight_entity fix. Stable kernel commits are referenced as fixes.
Likely exposure
Exposure is likely limited to Linux systems running affected upstream kernel versions or downstream kernels carrying the vulnerable commits. The source lists Linux 5.16, 5.15.27, 5.16.13, and 5.17 context, but distro-specific affected status must be confirmed from vendor advisories.
Exploitation context
No active exploitation is cited, and the CVE is not marked as KEV. The public bundle does not state exploit prerequisites, privilege requirements, or practical impact. Treat exploitability as unconfirmed from these sources.
Researcher notes
Evidence is sparse: no CVSS, CWE, exploit status, or impact description is provided. Analysis should focus on commit ancestry, distro backports, and whether sched_fork() fixes are present in deployed kernels.
Mitigation direction
Check kernel vendor advisories for CVE-2022-48944 coverage.
Update to a kernel containing the referenced stable fixes.
Prioritize shared or multi-user Linux systems for review.
Confirm appliance and cloud images inherit fixed downstream kernels.
Validation and detection
Inventory running kernel versions across Linux fleets.
Map distro kernel packages to the referenced stable commits.
Review vendor security trackers for fixed package versions.
Verify patched systems boot the updated kernel after maintenance.
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-48944 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.