Firecracker now rejects a huge memory request
Brief
This is not a guest path.
Notes
031a5fd6bed465fbffe751fd205da84776a39cd5 landed Wednesday on main (Jack Thomson), with prerequisite aad75879f924fc1c37b327d2df5110026e61330a. The convert-MiB-to-bytes helper shifted left by 20 and dropped the high bits, so 2^44 MiB became a 0-byte region. The size fields are now a 32-bit type (max just under 4 PiB). The wrap is rejected when the JSON is parsed. Swagger and CHANGELOG record the range.
firecracker-v1.16 and firecracker-v1.15 did not move. Latest published release remains v1.16.1 (2026-07-02). Anyone still on v1.16.1 does not have the check. The commits do not claim a guest trigger, a virtio overflow, a jailer miss, or a CVE.
Commit 031a5fd6bed465fbffe751fd205da84776a39cd5