Make dp_free_rib() safer#786
Open
PlagueCZ wants to merge 1 commit into
Open
Conversation
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.
In
dp_free_vni_data()the call todp_create_rib()can fail. If that happens, the pointervni_data->ipv4[socket_id]will be freed, but still present. Subsequent use of this pointer will result in use-after-free bug.Since there already was a wrapper for freeing this pointer, I simply added a set to NULL.
Sure in most cases the owning structure is immediately freed, so this could be optimized, but since such code seems to only be called rarely (VNI manipulation), I chose not to optimize, to make it cleaner.
Connected to #784