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, 04 Sep 2010 14:59:54 +0200 From: Jiri Slaby <jirislaby@...il.com> To: ddutt@...cade.com CC: rmody@...cade.com, "David S. Miller" <davem@...emloft.net>, ML netdev <netdev@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org> Subject: bna: potential null dereference Hi, stanse found a potential null dereference: bnad_cb_tx_cleanup -> struct bnad_unmap_q *unmap_q = tcb->unmap_q; -> -- tcb cannot be null now -- -> if (!tcb || (!tcb->unmap_q)) The thing is I have no idea whether the second parameter of cleanup may be null (move assignment after the check) or not (remove the check) Could you fix that? thanks, -- js -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists