Add advisory for ringbuf: panic-safety double-free in Consumer::skip/… - #3230
Merged
Merged
Conversation
djc
approved these changes
Sep 21, 2026
Member
|
Thanks! |
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
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.
Affected crate(s)
ringbuf(5,140,045 recent downloads per crates.io)Links to upstream issue(s) or PR(s)
Fixed in agerasev/ringbuf#60, released in 0.5.2.
Severity
Panic-safety unsoundness in
Consumer::skip/clear: the consumed elements are dropped before the read index is advanced, so a panicking elementDropleaves the read index pointing at already-dropped slots. TheLocalRbdestructor then drops them again — a double free (CWE-415) / use-after-free (CWE-416) reachable from safe Rust, confirmed under AddressSanitizer. Fixed in 0.5.2.Checklist
RUSTSEC-0000-0000as the IDdatefield is set to the public disclosure date