PT-2026-40734 · Crates.Io · Accessor
Published
2026-05-02
·
Updated
2026-05-02
None
No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
In
array::ReadWrite::new() (line 83 of accessor/src/array.rs),
let bytes = mem::size of::<T>() * len can overflow usize when len is
very large. In release mode, this silently wraps, potentially making
bytes = 0. The mapper then maps with 0 bytes, and subsequent accesses
(e.g. read volatile at) lead to undefined behavior or memory corruption.Note:
array::ReadWrite::new() itself is unsafe, so direct triggering
requires an unsafe block. However, the integer overflow violates the
implicit safety contract expected by callers and can lead to memory
corruption downstream. Found an issue in the description? Have something to add? Feel free to write us 👾
Related Identifiers
Affected Products
Accessor