linux-kernel - Re: [syzbot] BUG: unable to handle kernel paging request in dquot_add

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20221020085408.ebvapvm722t62c7q@quack3>
Date:   Thu, 20 Oct 2022 10:54:08 +0200
From:   Jan Kara <jack@...e.cz>
To:     syzbot <syzbot+7f3f0e8b232d8c69dac1@...kaller.appspotmail.com>
Cc:     jack@...e.com, linux-kernel@...r.kernel.org,
        syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] BUG: unable to handle kernel paging request in
 dquot_add_space

On Wed 19-10-22 23:37:39, syzbot wrote:
> HEAD commit:    bbed346d5a96 Merge branch 'for-next/core' into for-kernelci
> git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
> console output: https://syzkaller.appspot.com/x/log.txt?x=12890b76880000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=3a4a45d2d827c1e
> dashboard link: https://syzkaller.appspot.com/bug?extid=7f3f0e8b232d8c69dac1
> compiler:       Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
> userspace arch: arm64
> 
> Unfortunately, I don't have any reproducer for this issue yet.
> 
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/e8e91bc79312/disk-bbed346d.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/c1cb3fb3b77e/vmlinux-bbed346d.xz
> 
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+7f3f0e8b232d8c69dac1@...kaller.appspotmail.com
> 
> Unable to handle kernel paging request at virtual address 0000000100000117

Hum, this looks very much like some memory corruption because the where we
expect a pointer, there is (u32)-1 value... Let's wait if syzbot finds some
reproducer.

								Honza
-- 
Jan Kara <jack@...e.com>
SUSE Labs, CR