[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <fcbc5905-e507-6002-f5b2-95335c3d0083@i-love.sakura.ne.jp>
Date: Tue, 26 May 2020 21:58:29 +0900
From: Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>
To: syzbot <syzbot+cff8c4c75acd8c6fb842@...kaller.appspotmail.com>,
syzkaller-bugs@...glegroups.com
Cc: jmorris@...ei.org, linux-kernel@...r.kernel.org,
linux-security-module@...r.kernel.org, serge@...lyn.com
Subject: Re: general protection fault in tomoyo_check_acl
On 2020/05/26 12:46, syzbot wrote:
> general protection fault, probably for non-canonical address 0xe000026660000003: 0000 [#1] PREEMPT SMP KASAN
> KASAN: probably user-memory-access in range [0x0000333300000018-0x000033330000001f]
> CPU: 0 PID: 12489 Comm: systemd-rfkill Not tainted 5.7.0-rc6-syzkaller #0
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
> RIP: 0010:tomoyo_check_acl+0xa9/0x3e0 security/tomoyo/domain.c:173
struct tomoyo_acl_info *ptr == 0x0000333300000000 is strange; such pointer
can't be linked into standard doubly linked list using list_add_tail_rcu().
Thus, this report would to be an victim of memory corruption.
Powered by blists - more mailing lists