RUSTSEC-2025-0044

See a problem?
Please try reporting it to the source first.

Source

https://rustsec.org/advisories/RUSTSEC-2025-0044

Import Source

https://github.com/rustsec/advisory-db/blob/osv/crates/RUSTSEC-2025-0044.json

JSON Data

https://api.osv.dev/v1/vulns/RUSTSEC-2025-0044

Published

2025-06-16T12:00:00Z

Modified

2025-07-14T20:21:09Z

Summary

Four unique double-free vulnerabilities triggered via safe APIs

Details

The crate slice-ring-buffer was developed as a fork of slice-deque to continue maintenance and provide security patches, since the latter has been officially unmaintained (RUSTSEC-2020-0158).

While slice-ring-buffer has addressed some previously reported memory safety issues inherited from its fork origin (RUSTSEC-2021-0047), it still retains multiple unresolved memory corruption vulnerabilities.

Specifically, we have discovered four new memory safety bugs, each resulting in double-free violations that can occur when only safe APIs are invoked. These vulnerabilities correspond to four distinct safe APIs in the crate, each exposing unsound and vulnerable behavior due to incorrect usage of unsafe code internally.

Unfortunately, the maintainer doesn't have much availability to resolve these issues so there's no concrete timeline for fixes. Community contributions towards fixing these vulnerabilities would be much appreciated.

Database specific

{
    "license": "CC0-1.0"
}

References

Affected packages

crates.io / slice-ring-buffer

Package

Name: slice-ring-buffer; View open source insights on deps.dev
Purl: pkg:cargo/slice-ring-buffer

Affected ranges

Type: SEMVER
Events: Introduced

0.0.0-0

Ecosystem specific

{
    "affects": {
        "arch": [],
        "functions": [
            "slice_ring_buffer::IntoIter::clone",
            "slice_ring_buffer::SliceRingBuffer::extend_from_slice",
            "slice_ring_buffer::SliceRingBuffer::insert",
            "slice_ring_buffer::SliceRingBuffer::shrink_to_fit"
        ],
        "os": []
    },
    "affected_functions": null
}

Database specific

{
    "categories": [
        "memory-corruption"
    ],
    "informational": null,
    "cvss": null
}