Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
35 changes: 26 additions & 9 deletions src/guest_memory.rs
Original file line number Diff line number Diff line change
Expand Up @@ -654,15 +654,13 @@ pub trait GuestMemory {
Ok(0) => return Ok(total),
// made some progress
Ok(len) => {
total = match total.checked_add(len) {
Some(x) if x < count => x,
Some(x) if x == count => return Ok(x),
_ => return Err(Error::CallbackOutOfRange),
};
cur = match cur.overflowing_add(len as GuestUsize) {
(x @ GuestAddress(0), _) | (x, false) => x,
(_, true) => return Err(Error::GuestAddressOverflow),
};
total = total.checked_add(len).ok_or(Error::CallbackOutOfRange)?;
if total == count {
return Ok(total);
}
cur = cur
.checked_add(len as GuestUsize)
.ok_or(Error::GuestAddressOverflow)?;
}
// error happened
e => return e,
Expand Down Expand Up @@ -1304,6 +1302,25 @@ mod tests {
non_atomic_access_helper::<u16>()
}

#[cfg(feature = "backend-mmap")]
#[test]
// This test makes sure that computation for regions that end at u64::MAX do not cause
// overflows.
fn test_region_at_usize_max() {
let region_len: usize = 0x1000;
let addr = GuestAddress(u64::MAX - region_len as u64);
let mem = GuestMemoryMmap::from_ranges(&[(addr, region_len)]).unwrap();
let mut image = vec![0; region_len + 1];

// This access could cause an overflow if we wouldn't have a check for memory region length.
let invalid_access_size = region_len + 1;
let count = mem
.write_volatile_to(addr, &mut image.as_mut_slice(), invalid_access_size)
.unwrap();
// We can only write maximum region_len bytes.
assert_eq!(count, region_len);
}

#[cfg(feature = "backend-mmap")]
#[test]
fn test_zero_length_accesses() {
Expand Down