Fix undefined behavior in qsort comparison functions for rv_histogram #526
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.
The freq variable is of type size_t, but the qsort comparison functions were directly returning a->freq - b->freq, which implicitly converts the result to an int. This conversion can cause overflow, leading to implementation-defined behavior.
When freq values are sufficiently large, this issue may violate the antisymmetric and transitive properties required for comparison functions:
Antisymmetry: If a < b, then b > a.
Transitivity: If a < b and b < c, then a < c.
Violating these properties results in undefined behavior in qsort, which could trigger memory corruption in some glibc implementations, posing a potential security risk. [1]
Rewrite the comparison functions (cmp_dec and cmp_asc) to compare size_t values explicitly, ensuring correctness and avoiding overflow.
Link: https://www.qualys.com/2024/01/30/qsort.txt [1]