Answer in brief
CVE-2023-50711 records a Medium severity (CVSS 5.7) vulnerability in `serde` deserialization for `FamStructWrapper` lacks bound checks that could potentially lead to out-of-bounds memory access. The current sources do not mark it as known exploited. The current feed maps vmm-sys-util (crates.io). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.7. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps vmm-sys-util (crates.io). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| vmm-sys-utilcrates.io | >=0.5.0 <0.12.0 | 0.12.0 |
Published upstream
Jan 2, 2024
Evidence: source:osv:source_dates:source-dates:recordSource modified
Oct 12, 2026
Evidence: source:osv:source_dates:source-dates:recordFirst seen by HOL
Oct 12, 2026
## Impact An issue was discovered in the `FamStructWrapper::deserialize` implementation provided by the crate for `vmm_sys_util::fam::FamStructWrapper`, which can lead to out of bounds memory accesses. The deserialization does not check that the length stored in the header matches the flexible array length. Mismatch in the lengths might allow out of bounds memory access through Rust-safe methods. Impacted versions: >= 0.5.0 ## Patches The issue was corrected in version 0.12.0 by inserting a check that verifies the lengths of compared flexible arrays are equal for any deserialized header and aborting deserialization otherwise. Moreover, the API was changed so that header length can only be modified through Rust-unsafe code. This ensures that users cannot trigger out-of-bounds memory access from Rust-safe code.
Quoted source text, attributed separately from HOL analysis.