nhrpd: Fix nhrp_peer leak (backport #14579) #16165
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Addressed memory leak by removing
&c->peer_notifier
from the notifier list on termination. Retaining it caused the notifier list to stay active, preventing the deletion ofc->cur.peer
thereby causing a memory leak.Reordered termination steps to call
vrf_terminate
beforenhrp_vc_terminate
, preventing a heap-use-after-free issue whennhrp_vc_notify_del
is invoked innhrp_peer_check_delete
.Added an if statement to avoid passing NULL as hash to
hash_release
, which leads to a SIGSEGV.The ASan leak log for reference: