slab allows out-of-bounds access in `get_disjoint_mut` due to incorrect bounds check
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| tokio-rs | slab | affected |
|
No data.
No data.
| Vendor | Product | Versions |
|---|---|---|
| Tokio | Slab | — |
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2025-24190 | slab allows out-of-bounds access in `get_disjoint_mut` due to incorrect bounds check |
Github GHSA |
GHSA-qx2v-8332-m4fv | slab allows out-of-bounds access in `get_disjoint_mut` due to incorrect bounds check |
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.199% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Tokio
Tokio slab |
|
| Vendors & Products |
Tokio
Tokio slab |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | slab is a pre-allocated storage for a uniform data type. In version 0.4.10, the get_disjoint_mut method incorrectly checked if indices were within the slab's capacity instead of its length, allowing access to uninitialized memory. This could lead to undefined behavior or potential crashes. This has been fixed in slab 0.4.11. A workaround for this issue involves to avoid using get_disjoint_mut with indices that might be beyond the slab's actual length. | |
| Title | slab allows out-of-bounds access in `get_disjoint_mut` due to incorrect bounds check | |
| Weaknesses | CWE-119 | |
| References |
| |
| Metrics |
cvssV4_0
|