From: chenridong <chenridong@huawei.com>
To: Markus Elfring <Markus.Elfring@web.de>, <cgroups@vger.kernel.org>,
<bpf@vger.kernel.org>, Johannes Weiner <hannes@cmpxchg.org>,
Tejun Heo <tj@kernel.org>, Waiman Long <longman@redhat.com>,
Zefan Li <lizefan.x@bytedance.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] cgroup: fix uaf when proc_cpuset_show
Date: Mon, 24 Jun 2024 11:34:02 +0800 [thread overview]
Message-ID: <2d495a96-3ddd-4e8f-a055-159dc182cf8f@huawei.com> (raw)
In-Reply-To: <e1e51582-7ecb-40af-aae1-498993d0f935@web.de>
On 2024/6/22 21:45, Markus Elfring wrote:
>> We found a refcount UAF bug as follows:
>>
>> BUG: KASAN: use-after-free in cgroup_path_ns+0x112/0x150
> …
>
> How do you think about to use a summary phrase like “Avoid use-after-free
> in proc_cpuset_show()”?
>
>
>> This is also reported by: https://syzkaller.appspot.com/bug?extid=9b1ff7be974a403aa4cd
> Would you like to add any tags (like “Fixes”) accordingly?
>
Thank you for review, i will do that.
> …
>> +++ b/kernel/cgroup/cpuset.c
> …
>> @@ -5052,9 +5053,28 @@ int proc_cpuset_show(struct seq_file *m, struct pid_namespace *ns,
>> goto out;
>>
>> css = task_get_css(tsk, cpuset_cgrp_id);
>> + rcu_read_lock();
> …
>> + rcu_read_unlock();
>> retval = cgroup_path_ns(css->cgroup, buf, PATH_MAX,
>> current->nsproxy->cgroup_ns);
> …
>
> Would you become interested to apply a statement like “guard(rcu_read_lock)();”?
> https://elixir.bootlin.com/linux/v6.10-rc4/source/include/linux/cleanup.h#L133
>
> Regards,
> Markus
We hope somebody could have another better solution.
Regards
Ridong
next prev parent reply other threads:[~2024-06-24 3:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-22 11:38 [PATCH -next] cgroup: fix uaf when proc_cpuset_show Chen Ridong
2024-06-22 13:45 ` Markus Elfring
2024-06-24 3:34 ` chenridong [this message]
2024-06-22 15:05 ` Waiman Long
2024-06-22 20:04 ` [PATCH] cgroup/cpuset: Prevent UAF in proc_cpuset_show() Markus Elfring
2024-06-22 20:12 ` Waiman Long
2024-06-23 6:18 ` Markus Elfring
2024-06-23 16:28 ` Waiman Long
2024-06-24 2:59 ` [PATCH -next] cgroup: fix uaf when proc_cpuset_show chenridong
2024-06-24 23:59 ` Waiman Long
2024-06-25 1:46 ` chenridong
2024-06-25 2:40 ` Waiman Long
2024-06-25 3:12 ` chenridong
2024-06-25 10:10 ` Michal Koutný
[not found] ` <920bbfaa-bb76-4aa1-bd07-9a552e3bfdf2@huawei.com>
2024-06-25 14:16 ` Waiman Long
2024-06-25 14:29 ` chenridong
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=2d495a96-3ddd-4e8f-a055-159dc182cf8f@huawei.com \
--to=chenridong@huawei.com \
--cc=Markus.Elfring@web.de \
--cc=bpf@vger.kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan.x@bytedance.com \
--cc=longman@redhat.com \
--cc=tj@kernel.org \
/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