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
| ||
|
Date: Sat, 21 Nov 2020 13:09:12 -0800 From: Jakub Kicinski <kuba@...nel.org> To: Greg Kroah-Hartman <gregkh@...uxfoundation.org> Cc: Jamie Iles <jamie@...iainc.com>, netdev@...r.kernel.org, Qiushi Wu <wu000273@....edu>, Jay Vosburgh <j.vosburgh@...il.com>, Veaceslav Falico <vfalico@...il.com>, Andy Gospodarek <andy@...yhouse.net> Subject: Re: [PATCHv3] bonding: wait for sysfs kobject destruction before freeing struct slave On Fri, 20 Nov 2020 16:39:51 +0100 Greg Kroah-Hartman wrote: > On Fri, Nov 20, 2020 at 02:28:27PM +0000, Jamie Iles wrote: > > syzkaller found that with CONFIG_DEBUG_KOBJECT_RELEASE=y, releasing a > > struct slave device could result in the following splat: > > This is a potential use-after-free if the sysfs nodes are being accessed > > whilst removing the struct slave, so wait for the object destruction to > > complete before freeing the struct slave itself. > > Nice, it looks like it should have always been done this way! > > Reviewed-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org> Applied to net, thanks!
Powered by blists - more mailing lists