From: Tejun Heo <tj@kernel.org>
To: syzbot <syzbot+534ee3d24c37c411f37f@syzkaller.appspotmail.com>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com,
Christian Brauner <brauner@kernel.org>
Subject: Re: [syzbot] general protection fault in kernfs_get_inode
Date: Fri, 7 Oct 2022 11:35:49 -1000 [thread overview]
Message-ID: <Y0CbtVwW6+QIYJdQ@slm.duckdns.org> (raw)
In-Reply-To: <00000000000028a44005ea40352b@google.com>
(cc'ing Christian and quoting whole body)
Christan, I can't repro it here but think what we need is sth like the
following. The problem is that cgroup_is_dead() check in the fork path isn't
enough as the perm check depends on cgrp->procs_file being available but
that is cleared while DYING before DEAD. So, depending on the timing, we can
end up trying to deref NULL pointer in may_write.
diff --git a/kernel/cgroup/cgroup.c b/kernel/cgroup/cgroup.c
index 8ad2c267ff471..603b7167450a1 100644
--- a/kernel/cgroup/cgroup.c
+++ b/kernel/cgroup/cgroup.c
@@ -4934,6 +4934,10 @@ static int cgroup_may_write(const struct cgroup *cgrp, struct super_block *sb)
lockdep_assert_held(&cgroup_mutex);
+ /*if @cgrp is being removed, procs_file may already be gone */
+ if (!cgrp->procs_file.kn)
+ return -ENODEV;
+
inode = kernfs_get_inode(sb, cgrp->procs_file.kn);
if (!inode)
return -ENOMEM;
On Tue, Oct 04, 2022 at 07:19:34PM -0700, syzbot wrote:
> syzbot has found a reproducer for the following issue on:
>
> HEAD commit: 0326074ff465 Merge tag 'net-next-6.1' of git://git.kernel...
> git tree: upstream
> console+strace: https://syzkaller.appspot.com/x/log.txt?x=149c92cc880000
> kernel config: https://syzkaller.appspot.com/x/.config?x=e1de7ca9efcc028c
> dashboard link: https://syzkaller.appspot.com/bug?extid=534ee3d24c37c411f37f
> compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10af2492880000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=104874f0880000
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/43729d6ce2fc/disk-0326074f.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/1f76d6f68eb3/vmlinux-0326074f.xz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+534ee3d24c37c411f37f@syzkaller.appspotmail.com
>
> general protection fault, probably for non-canonical address 0xdffffc0000000012: 0000 [#1] PREEMPT SMP KASAN
> KASAN: null-ptr-deref in range [0x0000000000000090-0x0000000000000097]
> CPU: 1 PID: 3617 Comm: syz-executor384 Not tainted 6.0.0-syzkaller-02734-g0326074ff465 #0
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022
> RIP: 0010:kernfs_ino include/linux/kernfs.h:358 [inline]
> RIP: 0010:kernfs_get_inode+0x2e/0x520 fs/kernfs/inode.c:254
> Code: 41 56 41 55 41 54 49 89 fc 53 48 89 f3 e8 1a 04 7e ff 48 8d bb 90 00 00 00 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 3a 04 00 00 48 8b b3 90 00 00 00 4c 89 e7 e8 79
> RSP: 0018:ffffc90003c8fa30 EFLAGS: 00010206
> RAX: dffffc0000000000 RBX: 0000000000000000 RCX: 0000000000000000
> RDX: 0000000000000012 RSI: ffffffff81fd1156 RDI: 0000000000000090
> RBP: ffffc90003c8fa50 R08: 0000000000000005 R09: 0000000000000000
> R10: 0000000000000001 R11: 0000000000000024 R12: ffff8880224ba000
> R13: ffff888075922000 R14: ffff88801ebf0000 R15: ffff8880211ae000
> FS: 0000555556907300(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 0000000020000200 CR3: 000000001c179000 CR4: 00000000003506e0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> Call Trace:
> <TASK>
> cgroup_may_write+0x86/0x120 kernel/cgroup/cgroup.c:4937
> cgroup_css_set_fork kernel/cgroup/cgroup.c:6237 [inline]
> cgroup_can_fork+0x961/0xec0 kernel/cgroup/cgroup.c:6331
> copy_process+0x43ed/0x7090 kernel/fork.c:2358
> kernel_clone+0xe7/0xab0 kernel/fork.c:2671
> __do_sys_clone3+0x1cd/0x2e0 kernel/fork.c:2963
> do_syscall_x64 arch/x86/entry/common.c:50 [inline]
> do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
> entry_SYSCALL_64_after_hwframe+0x63/0xcd
> RIP: 0033:0x7f621d8c3e99
> Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 51 15 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48
> RSP: 002b:00007ffcaa952ec8 EFLAGS: 00000206 ORIG_RAX: 00000000000001b3
> RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007f621d8c3e99
> RDX: 0000000000000000 RSI: 0000000000000058 RDI: 00007ffcaa952f40
> RBP: 0000000000000000 R08: 00007ffcaa952d60 R09: 00007ffcaa952ef0
> R10: 00000000ffffffff R11: 0000000000000206 R12: 00007ffcaa952eec
> R13: 00007ffcaa952f00 R14: 00007ffcaa952f40 R15: 0000000000000000
> </TASK>
> Modules linked in:
> ---[ end trace 0000000000000000 ]---
> RIP: 0010:kernfs_ino include/linux/kernfs.h:358 [inline]
> RIP: 0010:kernfs_get_inode+0x2e/0x520 fs/kernfs/inode.c:254
> Code: 41 56 41 55 41 54 49 89 fc 53 48 89 f3 e8 1a 04 7e ff 48 8d bb 90 00 00 00 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 3a 04 00 00 48 8b b3 90 00 00 00 4c 89 e7 e8 79
> RSP: 0018:ffffc90003c8fa30 EFLAGS: 00010206
> RAX: dffffc0000000000 RBX: 0000000000000000 RCX: 0000000000000000
> RDX: 0000000000000012 RSI: ffffffff81fd1156 RDI: 0000000000000090
> RBP: ffffc90003c8fa50 R08: 0000000000000005 R09: 0000000000000000
> R10: 0000000000000001 R11: 0000000000000024 R12: ffff8880224ba000
> R13: ffff888075922000 R14: ffff88801ebf0000 R15: ffff8880211ae000
> FS: 0000555556907300(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 00007ffcaa9cb8f0 CR3: 000000001c179000 CR4: 00000000003506f0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> ----------------
> Code disassembly (best guess):
> 0: 41 56 push %r14
> 2: 41 55 push %r13
> 4: 41 54 push %r12
> 6: 49 89 fc mov %rdi,%r12
> 9: 53 push %rbx
> a: 48 89 f3 mov %rsi,%rbx
> d: e8 1a 04 7e ff callq 0xff7e042c
> 12: 48 8d bb 90 00 00 00 lea 0x90(%rbx),%rdi
> 19: 48 b8 00 00 00 00 00 movabs $0xdffffc0000000000,%rax
> 20: fc ff df
> 23: 48 89 fa mov %rdi,%rdx
> 26: 48 c1 ea 03 shr $0x3,%rdx
> * 2a: 80 3c 02 00 cmpb $0x0,(%rdx,%rax,1) <-- trapping instruction
> 2e: 0f 85 3a 04 00 00 jne 0x46e
> 34: 48 8b b3 90 00 00 00 mov 0x90(%rbx),%rsi
> 3b: 4c 89 e7 mov %r12,%rdi
> 3e: e8 .byte 0xe8
> 3f: 79 .byte 0x79
>
--
tejun
next prev parent reply other threads:[~2022-10-07 21:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 0:59 [syzbot] general protection fault in kernfs_get_inode syzbot
2022-10-05 2:19 ` syzbot
2022-10-07 21:35 ` Tejun Heo [this message]
2022-10-08 5:46 ` Christian Brauner
2022-10-08 5:51 ` Christian Brauner
2022-10-08 11:15 ` syzbot
2022-10-08 18:29 ` Christian A. Ehrhardt
2022-10-09 8:42 ` Christian Brauner
2022-10-09 13:10 ` [PATCH] cgroup: Fix crash with CLONE_INTO_CGROUP and v1 cgroups Christian A. Ehrhardt
2022-10-09 17:35 ` Christian Brauner
2022-10-09 18:16 ` Greg KH
2022-10-10 18:48 ` Tejun Heo
2022-10-09 18:42 ` Yosry Ahmed
2022-10-10 18:38 ` Martin KaFai Lau
2022-10-10 18:43 ` Tejun Heo
2022-10-10 18:50 ` Yosry Ahmed
2022-10-10 19:51 ` Tejun Heo
2022-10-10 19:57 ` Yosry Ahmed
2022-10-10 20:07 ` Tejun Heo
2022-10-10 20:09 ` Yosry Ahmed
2022-11-17 7:26 ` [syzbot] general protection fault in kernfs_get_inode syzbot
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=Y0CbtVwW6+QIYJdQ@slm.duckdns.org \
--to=tj@kernel.org \
--cc=brauner@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+534ee3d24c37c411f37f@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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;
as well as URLs for NNTP newsgroup(s).