[Pkg-rust-maintainers] Bug#1051101: rust-vm-memory: CVE-2023-41051

[Salvatore Bonaccorso]

Source: rust-vm-memory
Version: 0.12.0-2
Severity: important
Tags: security upstream
X-Debbugs-Cc: carnil at debian.org, Debian Security Team <team at security.debian.org>

Hi,

The following vulnerability was published for rust-vm-memory.

CVE-2023-41051[0]:
| In a typical Virtual Machine Monitor (VMM) there are several
| components, such as boot loader, virtual device drivers, virtio
| backend drivers and vhost drivers, that need to access the VM
| physical memory. The vm-memory rust crate provides a set of traits
| to decouple VM memory consumers from VM memory providers. An issue
| was discovered in the default implementations of the
| `VolatileMemory::{get_atomic_ref, aligned_as_ref, aligned_as_mut,
| get_ref, get_array_ref}` trait functions, which allows out-of-bounds
| memory access if the `VolatileMemory::get_slice` function returns a
| `VolatileSlice` whose length is less than the function’s `count`
| argument. No implementations of `get_slice` provided in `vm_memory`
| are affected. Users of custom `VolatileMemory` implementations may
| be impacted if the custom implementation does not adhere to
| `get_slice`'s documentation. The issue started in version 0.1.0 but
| was fixed in version 0.12.2 by inserting a check that verifies that
| the `VolatileSlice` returned by `get_slice` is of the correct
| length. Users are advised to upgrade. There are no known workarounds
| for this issue.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-41051
    https://www.cve.org/CVERecord?id=CVE-2023-41051
[1] https://github.com/rust-vmm/vm-memory/security/advisories/GHSA-49hh-fprx-m68g
[2] https://github.com/rust-vmm/vm-memory/commit/aff1dd4a5259f7deba56692840f7a2d9ca34c9c8

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore