ill_lookup_on_ifindex_global_instance() could leak netstack ids
The way that this function works, if it fails to find an ip_stack for the global zone, it would end up leaking the netstack associated with it. While it's rare, it seems like this could leak a netstack reference, though it's only for the global zone, which likely will never be destroyed until shutdown and even then, it's pretty rare not to have the ip stack.
Updated by Electric Monk over 4 years ago
- Status changed from New to Closed
commit 854956ce2a18fd37e3f6160d38ffb87fdbc2edc4 Author: Bryan Cantrill <firstname.lastname@example.org> Date: 2016-10-11T18:14:30.000Z 7413 netstack leaks lead to blind netstack reuse 7414 iptun leaks netstacks 7415 ipnet_promisc_add() leaks netstacks in error paths 7416 ill_lookup_on_ifindex_global_instance() could leak netstack ids Reviewed by: Jerry Jelinek <email@example.com> Reviewed by: Robert Mustacchi <firstname.lastname@example.org> Reviewed by: Sebastien Roy <email@example.com> Approved by: Dan McDonald <firstname.lastname@example.org>