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
| ||
|
Message-ID: <20220109132038.38f8ae4f@kicinski-fedora-PC1C0HJN.hsd1.ca.comcast.net> Date: Sun, 9 Jan 2022 13:20:38 -0800 From: Jakub Kicinski <kuba@...nel.org> To: Lukas Bulwahn <lukas.bulwahn@...il.com> Cc: Rao Shoaib <rao.shoaib@...cle.com>, "David S. Miller" <davem@...emloft.net>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Netdev <netdev@...r.kernel.org>, Sudip Mukherjee <sudip.mukherjee@...ethink.co.uk>, regressions@...ts.linux.dev Subject: Re: Observation of a memory leak with commit 314001f0bf92 ("af_unix: Add OOB support") On Fri, 7 Jan 2022 07:48:46 +0100 Lukas Bulwahn wrote: > Dear Rao and David, > > > In our syzkaller instance running on linux-next, > https://elisa-builder-00.iol.unh.edu/syzkaller-next/, we have been > observing a memory leak in prepare_creds, > https://elisa-builder-00.iol.unh.edu/syzkaller-next/report?id=1dcac8539d69ad9eb94ab2c8c0d99c11a0b516a3, > for quite some time. > > It is reproducible on v5.15-rc1, v5.15, v5.16-rc8 and next-20220104. > So, it is in mainline, was released and has not been fixed in > linux-next yet. > > As syzkaller also provides a reproducer, we bisected this memory leak > to be introduced with commit 314001f0bf92 ("af_unix: Add OOB > support"). > > We also tested that reverting this commit on torvalds' current tree > made the memory leak with the reproducer go away. > > Could you please have a look how your commit introduces this memory > leak? We will gladly support testing your fix in case help is needed. Let's test the regression/bug report tracking bot :) #regzbot introduced: 314001f0bf92
Powered by blists - more mailing lists