From: "Mickaël Salaün" <mic@digikod.net>
To: Ubisectech Sirius <bugreport@ubisectech.com>
Cc: linux-trace-kernel <linux-trace-kernel@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-security-module <linux-security-module@vger.kernel.org>,
"Günther Noack" <gnoack@google.com>
Subject: Re: 回复：WARNING in current_check_refer_path
Date: Mon, 29 Apr 2024 16:46:19 +0200 [thread overview]
Message-ID: <20240429.ieR4Ajeitee5@digikod.net> (raw)
In-Reply-To: <d36cf38a-a22a-44ec-b606-b58ccc559a47.bugreport@ubisectech.com>
On Mon, Apr 29, 2024 at 05:16:57PM +0800, Ubisectech Sirius wrote:
> > Hello,
>
> > Thanks for the report. Could you please provide a reproducer?
>
> > Regards,
> > Mickaël
>
> Hi.
> The Poc file has seed to you as attachment.
Indeed, but could you please trim down the file. There are 650 lines,
most of them are irrelevant.
>
> > On Sun, Apr 28, 2024 at 10:47:02AM +0800, Ubisectech Sirius wrote:
> >> Hello.
> >> We are Ubisectech Sirius Team, the vulnerability lab of China ValiantSec. Recently, our team has discovered a issue in Linux kernel 6.7. Attached to the email were a PoC file of the issue.
> >>
> >> Stack dump:
> >>
> > > loop3: detected capacity change from 0 to 1024
> > > ------------[ cut here ]------------
> > > WARNING: CPU: 0 PID: 30368 at security/landlock/fs.c:598 get_mode_access security/landlock/fs.c:598 [inline]
> > > WARNING: CPU: 0 PID: 30368 at security/landlock/fs.c:598 get_mode_access security/landlock/fs.c:578 [inline]
> > > WARNING: CPU: 0 PID: 30368 at security/landlock/fs.c:598 current_check_refer_path+0x955/0xa60 security/landlock/fs.c:758
> > > Modules linked in:
> > > CPU: 0 PID: 30368 Comm: syz-executor.3 Not tainted 6.7.0 #2
> > > Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014
> > > RIP: 0010:get_mode_access security/landlock/fs.c:598 [inline]
> > > RIP: 0010:get_mode_access security/landlock/fs.c:578 [inline]
> > > RIP: 0010:current_check_refer_path+0x955/0xa60 security/landlock/fs.c:758
> > > Code: e9 76 fb ff ff 41 bc fe ff ff ff e9 6b fb ff ff e8 00 99 77 fd 90 0f 0b 90 41 bc f3 ff ff ff e9 57 fb ff ff e8 ec 98 77 fd 90 <0f> 0b 90 31 db e9 86 f9 ff ff bb 00 08 00 00 e9 7c f9 ff ff 41 ba
> > > RSP: 0018:ffffc90001fb7ba0 EFLAGS: 00010212
> > > RAX: 0000000000000bc5 RBX: ffff88805feeb7b0 RCX: ffffc90006e15000
> > > RDX: 0000000000040000 RSI: ffffffff84125d64 RDI: 0000000000000003
> > > RBP: ffff8880123c5608 R08: 0000000000000003 R09: 000000000000c000
> > > R10: 000000000000f000 R11: 0000000000000000 R12: ffff88805d32fc00
> > > R13: ffff8880123c5608 R14: 0000000000000000 R15: 0000000000000001
> > > FS: 00007fd70c4d8640(0000) GS:ffff88802c600000(0000) knlGS:0000000000000000
> > > CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> > > CR2: 0000001b2c136000 CR3: 000000005b2a0000 CR4: 0000000000750ef0
> > > DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> > > DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> > > PKRU: 55555554
> > > Call Trace:
> > > <TASK>
> > > security_path_rename+0x124/0x230 security/security.c:1828
> > > do_renameat2+0x9f6/0xd30 fs/namei.c:4983
> > > __do_sys_rename fs/namei.c:5042 [inline]
> > > __se_sys_rename fs/namei.c:5040 [inline]
> > > __x64_sys_rename+0x81/0xa0 fs/namei.c:5040
> > > do_syscall_x64 arch/x86/entry/common.c:52 [inline]
> > > do_syscall_64+0x43/0x120 arch/x86/entry/common.c:83
> > > entry_SYSCALL_64_after_hwframe+0x6f/0x77
> > > RIP: 0033:0x7fd70b6900ed
> > > Code: c3 e8 97 2b 00 00 0f 1f 80 00 00 00 00 f3 0f 1e fa 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 b0 ff ff ff f7 d8 64 89 01 48
> > > RSP: 002b:00007fd70c4d8028 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
> > > RAX: ffffffffffffffda RBX: 00007fd70b7cbf80 RCX: 00007fd70b6900ed
> >> RDX: 0000000000000000 RSI: 0000000020000140 RDI: 0000000020000100
> > > RBP: 00007fd70b6f14a6 R08: 0000000000000000 R09: 0000000000000000
> > > R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
> > > R13: 000000000000000b R14: 00007fd70b7cbf80 R15: 00007fd70c4b8000
> > > </TASK>
> > >
> > > Thank you for taking the time to read this email and we look forward to working with you further.
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
>
>
prev parent reply other threads:[~2024-04-29 14:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c426821d-8380-46c4-a494-7008bbd7dd13.bugreport@ubisectech.com>
2024-04-29 9:05 ` WARNING in current_check_refer_path Mickaël Salaün
2024-04-29 9:16 ` 回复：WARNING " Ubisectech Sirius
2024-04-29 14:46 ` Mickaël Salaün [this message]
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=20240429.ieR4Ajeitee5@digikod.net \
--to=mic@digikod.net \
--cc=bugreport@ubisectech.com \
--cc=gnoack@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=linux-trace-kernel@vger.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).