From: Xia Fukun <xiafukun@huawei.com>
To: <cve@kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-cve-announce@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Zhangqiao (2012 lab)" <zhangqiao22@huawei.com>,
"Chenhui (Judy)" <judy.chenhui@huawei.com>
Subject: Re: CVE-2022-48921: sched/fair: Fix fault in reweight_entity
Date: Sat, 24 Aug 2024 17:52:05 +0800 [thread overview]
Message-ID: <c0aa1e66-8e85-6aa0-e933-d5b6e3a2e3e7@huawei.com> (raw)
In-Reply-To: <2024082218-CVE-2022-48921-5016@gregkh>
On 2024/8/22 11:31, Greg Kroah-Hartman wrote:
> Description
> ===========
>
> 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.
>
>
> The Linux kernel CVE team has assigned CVE-2022-48921 to this issue.
>
Commit 13765de8148f ("sched/fair: Fix fault in reweight_entity")
is reverted by commit b1e8206582f9 ("sched: Fix yet more sched_fork()
races"). Since commit 13765de8148f only fixes a single instance
of this problem, not the whole class.
I think the CVE-2022-48921 needs to adjust the corresponding commit
to commit b1e8206582f9 ("sched: Fix yet more sched_fork() races").
next parent reply other threads:[~2024-08-24 9:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2024082218-CVE-2022-48921-5016@gregkh>
2024-08-24 9:52 ` Xia Fukun [this message]
2024-08-25 5:54 ` Greg Kroah-Hartman
2024-08-30 10:45 ` Greg Kroah-Hartman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c0aa1e66-8e85-6aa0-e933-d5b6e3a2e3e7@huawei.com \
--to=xiafukun@huawei.com \
--cc=cve@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=judy.chenhui@huawei.com \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zhangqiao22@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®