DFs in slice-ring-buffer #2336
Open
DFs in slice-ring-buffer #2336
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
|
@LiquidityC please confirm that you are okay with an advisory being published for your crate. Also, are you planning to fix these issues? If that is planned for the short term, we typically like to hold off on publishing an advisory until the fixed version is published. |
djc
reviewed
Jun 17, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Four new memory safety bugs have been discovered in
slice-ring-buffer(a fork of the unmaintainedslice-dequecrate).All four bugs can lead to double-free violations, when only safe APIs are used. No patches for these vulnerabilities have been developed yet.
We have contacted the maintainers of the crate (@LiquidityC), and they have granted us permission to request a security advisory for these issues.