{"answers":{"affected":"1 open source package ship an affected version, including oneringbuf.","exploited":"There is no known exploitation of RUSTSEC-2026-0143 in the wild and no public exploit code.","fix":"Upgrade oneringbuf to 0.7.1 or later.","what":"RUSTSEC-2026-0143 is an use after free vulnerability in oneringbuf, published on 14 May 2026."},"fix_prompt":"Check this codebase for RUSTSEC-2026-0143 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0143 is an use after free vulnerability in oneringbuf, published on 14 May 2026. \nExploitation: There is no known exploitation of RUSTSEC-2026-0143 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- oneringbuf (crates.io): affected from 0.0.0-0; fixed in 0.7.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/RUSTSEC-2026-0143/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0143/index.md)","id":"RUSTSEC-2026-0143","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0143/index.md","name":"RUSTSEC-2026-0143","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service","code_execution"],"network_reachable":"unknown","non_default_config":true,"product_category":"Rust ring buffer library","requires_auth":"none","summary":"A double-free vulnerability in the vmem feature allows attackers to cause crashes or potentially execute code via memory corruption when using safe Rust constructors.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"When the `vmem` feature is enabled, `VmemStorage\u003cT\u003e::new(Box\u003c[UnsafeSyncCell\u003cT\u003e]\u003e)` (and every public constructor that funnels through it — `ConcurrentHeapRB::default(cap)`, `ConcurrentHeapRB::from(Vec\u003cT\u003e)`, `From\u003cBox\u003c[T]\u003e\u003e`, etc.) bit-copies the input buffer into a freshly `mmap`'d region with `ptr::copy_nonoverlapping`, then lets the source `Box\u003c[UnsafeSyncCell\u003cT\u003e]\u003e` drop normally.\n\nBecause `UnsafeSyncCell\u003cT\u003e` has a `Drop` impl that runs `assume_init_drop` on its inner `MaybeUninit\u003cT\u003e`, the source-side `T` values are dropped at the end of `new`, while bitwise duplicates (carrying the same heap pointers for `String`, `Box`, `Vec`, `Arc`, …) remain inside the mmap region. When the ring buffer is later destructed, the destructor's `drop_in_place` over the slice runs `UnsafeSyncCell::drop` a second time on every cell — a deterministic double-free of every heap-owning element. Reachable from 100% safe Rust.\n\n## Trigger\n\n```rust\nlet v: Vec\u003cVec\u003cu32\u003e\u003e = (0..1024).map(|i| vec![i, i+1, i+2]).collect();\nlet rb: oneringbuf::SharedVmemRB\u003cVec\u003cu32\u003e\u003e = oneringbuf::SharedVmemRB::from(v);\ndrop(rb);\n// glibc: free(): double free detected in tcache 2 -\u003e abort\n// ASan: AddressSanitizer: attempting double-free\n```\n\nAny `T` with a non-trivial `Drop` reproduces deterministically.\n\n## Fix\n\nFixed in `0.7.1` via upstream PR [skilvingr/rust-oneringbuf#3](https://github.com/skilvingr/rust-oneringbuf/pull/3), which deallocates the source `Box\u003c[UnsafeSyncCell\u003cT\u003e]\u003e` without running per-element `Drop` after the bytes have been copied into the mmap region. Vulnerable versions (`\u003c 0.7.1`) have been yanked from crates.io.","ecosystems":["crates.io"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Double-free in `vmem` storage reachable from safe Rust","id":"RUSTSEC-2026-0143","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["0.7.1"],"introduced":["0.0.0-0"],"last_affected":[],"package":"oneringbuf","purl":"pkg:cargo/oneringbuf","source":"RUSTSEC-2026-0143"}],"products":null,"published":"2026-05-14","related":[],"sources":[{"class":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"A double-free vulnerability in the vmem feature allows attackers to cause crashes or potentially execute code via memory corruption when using safe Rust constructors.","url":"https://insights.sbomify.com/RUSTSEC-2026-0143/"}