eigrpd: handle the gr neighbor list safely in update_receive (backport #20933)#20938
Merged
donaldsharp merged 1 commit intostable/10.5from Feb 25, 2026
Merged
Conversation
Be careful handling the gr neighbor list; don't free the list if it's present in the neighbor struct. Reported-by: Sin Liang Lee <slee3846@gatech.edu> Signed-off-by: Mark Stapp <mjs@cisco.com> (cherry picked from commit d3d7f1d)
|
Target branch is not in the allowed branches list. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Be careful handling the gr neighbor list; don't free the list if it's present in the neighbor struct. Reported by a team at Ga Tech.
This is an automatic backport of pull request #20933 done by [Mergify](https://mergify.com).