linux-kernel - Re: [syzbot] memory leak in ___neigh

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 for Android: free password hash cracker in your pocket

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

Message-ID: <000000000000ef47400616631ea7@google.com>
Date: Thu, 18 Apr 2024 11:27:16 -0700
From: syzbot <syzbot+42cfec52b6508887bbe8@...kaller.appspotmail.com>
To: alexander.mikhalitsyn@...tuozzo.com, davem@...emloft.net, den@...nvz.org, 
	dsahern@...nel.org, edumazet@...gle.com, f.fainelli@...il.com, 
	kuba@...nel.org, linux-kernel@...r.kernel.org, netdev@...r.kernel.org, 
	nogikh@...gle.com, pabeni@...hat.com, razor@...ckwall.org, 
	syzkaller-bugs@...glegroups.com, thomas.zeitlhofer+lkml@...it.at, 
	thomas.zeitlhofer@...it.at, wangyuweihx@...il.com
Subject: Re: [syzbot] memory leak in ___neigh_create (2)

This bug is marked as fixed by commit:
net: stop syzbot

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=42cfec52b6508887bbe8

---
[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 9 trees can be found at
https://syzkaller.appspot.com/upstream/repos