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: <20190208.223257.815387749876892346.davem@davemloft.net> Date: Fri, 08 Feb 2019 22:32:57 -0800 (PST) From: David Miller <davem@...emloft.net> To: pabeni@...hat.com Cc: netdev@...r.kernel.org, jhansen@...are.com, sgarzare@...hat.com Subject: Re: [PATCH net] vsock: cope with memory allocation failure at socket creation time From: Paolo Abeni <pabeni@...hat.com> Date: Thu, 7 Feb 2019 14:13:18 +0100 > In the unlikely event that the kmalloc call in vmci_transport_socket_init() > fails, we end-up calling vmci_transport_destruct() with a NULL vmci_trans() > and oopsing. > > This change addresses the above explicitly checking for zero vmci_trans() > at destruction time. > > Reported-by: Xiumei Mu <xmu@...hat.com> > Fixes: d021c344051a ("VSOCK: Introduce VM Sockets") > Signed-off-by: Paolo Abeni <pabeni@...hat.com> Applied and queued up for -stable, thanks.
Powered by blists - more mailing lists