linux-kernel - Re: [syzbot] general protection fault in lock_vma_under

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: <68342b47.a70a0220.253bc2.0090.GAE@google.com>
Date: Mon, 26 May 2025 01:50:15 -0700
From: syzbot <syzbot+556fda2d78f9b0daa141@...kaller.appspotmail.com>
To: akpm@...ux-foundation.org, asml.silence@...il.com, axboe@...nel.dk, 
	eadavis@...com, io-uring@...r.kernel.org, linux-kernel@...r.kernel.org, 
	linux-mm@...ck.org, shivankg@....com, surenb@...gle.com, 
	syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] general protection fault in lock_vma_under_rcu

This bug is marked as fixed by commit:
mm: fix a crash due to vma_end_read() that should have been removed

But I can't find it in the tested trees[1] for more than 90 days.
Is it a correct commit? Please update it by replying:

#syz fix: exact-commit-title

Until then the bug is still considered open and new crashes with
the same signature are ignored.

Kernel: Linux
Dashboard link: https://syzkaller.appspot.com/bug?extid=556fda2d78f9b0daa141

---
[1] I expect the commit to be present in:

1. for-kernelci branch of
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git

2. master branch of
git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git

3. master branch of
git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git

4. main branch of
git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git

The full list of 10 trees can be found at
https://syzkaller.appspot.com/upstream/repos