Lucene search

K
vulnrichmentLinuxVULNRICHMENT:CVE-2022-48921
HistoryAug 22, 2024 - 1:32 a.m.

CVE-2022-48921 sched/fair: Fix fault in reweight_entity

2024-08-2201:32:53
Linux
github.com
linux kernel
vulnerability
reweight_entity
race
null pointer dereference
sched_post_fork
setpriority
copy_process
update_load param
task_new flag

AI Score

6.8

Confidence

Low

EPSS

0

Percentile

5.1%

SSVC

Exploitation

none

Automatable

no

Technical Impact

partial

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.

AI Score

6.8

Confidence

Low

EPSS

0

Percentile

5.1%

SSVC

Exploitation

none

Automatable

no

Technical Impact

partial

Related for VULNRICHMENT:CVE-2022-48921