RUSTSEC-2025-0162
`VMABuffer::set_data` may allow out-of-bounds writes from safe code
VMABuffer::set_data was a publicly accessible safe function. It accepted an arbitrary offset and a data slice, then used the offset in unsafe pointer arithmetic before copying the slice into a mapped allocation.
Affected versions did not check that the requested write range fit within the allocation before calling ptr.add(offset) and copy_from_nonoverlapping. Safe Rust code could therefore trigger an out-of-bounds write by passing an offset outside the mapped allocation.
This makes the safe API unsound, since callers can trigger undefined behavior without using unsafe.
Version 0.4.0 added a bounds check before performing the pointer arithmetic and copy.
What each source reports
OSV No score
`VMABuffer::set_data` may allow out-of-bounds writes from safe code
VMABuffer::set_data was a publicly accessible safe function. It accepted an arbitrary offset and a data slice, then used the offset in unsafe pointer arithmetic before copying the slice into a mapped allocation.
Affected versions did not check that the requested write range fit within the allocation before calling ptr.add(offset) and copy_from_nonoverlapping. Safe Rust code could therefore trigger an out-of-bounds write by passing an offset outside the mapped allocation.
This makes the safe API unsound, since callers can trigger undefined behavior without using unsafe.
Version 0.4.0 added a bounds check before performing the pointer arithmetic and copy.
- Record
RUSTSEC-2025-0162- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
vkucrates.io |
0.0.0-0 up to 0.4.0 | 0.4.0 |
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
RUSTSEC-2025-0162 is a vulnerability with no CVSS score yet in vku, published April 23, 2025. No source lists public exploit code. Fixed in vku 0.4.0.