rustsec-2026-0133
Vulnerability from osv_rustsec
Published
2026-05-02 12:00
Modified
2026-05-13 12:38
Summary
Invalid pointer arithmetic in `iter()` and `iter_mut()`
Details
The iter() and iter_mut() APIs compute
current = (&children[0] as *const *const RawAutoChild).sub(1), which
performs pointer subtraction going before the start of the allocation. This
is undefined behavior per Rust's pointer arithmetic rules.
This can be triggered through safe public APIs — iter() and iter_mut()
— with no unsafe required from the caller.
{
"affected": [
{
"database_specific": {
"categories": [
"memory-corruption"
],
"cvss": null,
"informational": "unsound"
},
"ecosystem_specific": {
"affected_functions": null,
"affects": {
"arch": [],
"functions": [],
"os": []
}
},
"package": {
"ecosystem": "crates.io",
"name": "auto_vec",
"purl": "pkg:cargo/auto_vec"
},
"ranges": [
{
"events": [
{
"introduced": "0.0.0-0"
}
],
"type": "SEMVER"
}
],
"versions": []
}
],
"aliases": [],
"database_specific": {
"license": "CC0-1.0"
},
"details": "The `iter()` and `iter_mut()` APIs compute\n`current = (\u0026children[0] as *const *const RawAutoChild).sub(1)`, which\nperforms pointer subtraction going before the start of the allocation. This\nis undefined behavior per Rust\u0027s pointer arithmetic rules.\n\nThis can be triggered through safe public APIs \u2014 `iter()` and `iter_mut()`\n\u2014 with no `unsafe` required from the caller.",
"id": "RUSTSEC-2026-0133",
"modified": "2026-05-13T12:38:12Z",
"published": "2026-05-02T12:00:00Z",
"references": [
{
"type": "PACKAGE",
"url": "https://crates.io/crates/auto_vec"
},
{
"type": "ADVISORY",
"url": "https://rustsec.org/advisories/RUSTSEC-2026-0133.html"
},
{
"type": "REPORT",
"url": "https://github.com/lluvz/AutoVec/issues/1"
}
],
"related": [],
"severity": [],
"summary": "Invalid pointer arithmetic in `iter()` and `iter_mut()`"
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…