fix(tools): fix NULL pointer dereference in output_fname allocation and set output_fname to NULL after freeing to prevent dangling pointer#28
Open
vahagavagyan wants to merge 2 commits into
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.
Description
This PR fixes a potential NULL pointer dereference vulnerability in
fftw-wisdom.c(or benchmark utility) inside the handling of the-oflag.Missing validation
The current implementation calls
strcpy(output_fname, my_optarg);immediately after callingbench_malloc(), without verifying if the memory allocation succeeded. Ifbench_mallocreturnsNULLdue to memory exhaustion, it causes a crash (Segmentation Fault).Changes
bench_malloc.output_fnameafterbench_freeto avoid potential dangling pointer issues.