Slice Ring Buffer and Slice Deque contains four unique double-free vulnerabilities triggered through safe APIs

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.1 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U · score source

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

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.

Published by the source

16 Jul 2025, 14:18 UTC

Last modified by the source

16 Jul 2025, 14:18 UTC

Source last checked

26 Oct 2026, 15:38 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-7mcq-f592-pf7v

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-7mcq-f592-pf7v

Advisory: Slice Ring Buffer and Slice Deque contains four unique double-free vulnerabilities triggered through safe APIs
IDs: GHSA-7mcq-f592-pf7v
Record: https://patchnext.com/advisories/ghsa-7mcq-f592-pf7v (revision 1, source checked 26 Oct 2026, 15:38 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io slice-deque: affected <= 0.3.0
- crates.io slice-ring-buffer: affected <= 0.3.4

## Suggested inspection (read-only)
- crates.io slice-deque: check the installed version with your package manager.
- crates.io slice-ring-buffer: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on slice-deque, slice-ring-buffer.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-7mcq-f592-pf7v (GitHub-reviewed advisory GHSA-7mcq-f592-pf7v lists affected ranges: crates.io slice-deque >=0 =0 <=0.3.4)

Commands are suggestions: review each one before running it.