Описание
bytes has integer overflow in BytesMut::reserve
Details
In the unique reclaim path of BytesMut::reserve, the condition
uses an unchecked addition. When new_cap + offset overflows usize in release builds, this condition may incorrectly pass, causing self.cap to be set to a value that exceeds the actual allocated capacity. Subsequent APIs such as spare_capacity_mut() then trust this corrupted cap value and may create out-of-bounds slices, leading to UB.
This behavior is observable in release builds (integer overflow wraps), whereas debug builds panic due to overflow checks.
PoC
Workarounds
Users of BytesMut::reserve are only affected if integer overflow checks are configured to wrap. When integer overflow is configured to panic, this issue does not apply.
This vulnerability is also known as RUSTSEC-2026-0007.
Ссылки
- https://github.com/tokio-rs/bytes/security/advisories/GHSA-434x-w66g-qw3r
- https://nvd.nist.gov/vuln/detail/CVE-2026-25541
- https://github.com/tokio-rs/bytes/commit/d0293b0e35838123c51ca5dfdf468ecafee4398f
- https://github.com/tokio-rs/bytes/releases/tag/v1.11.1
- https://rustsec.org/advisories/RUSTSEC-2026-0007.html
Пакеты
bytes
>= 1.2.1, < 1.11.1
1.11.1
Связанные уязвимости
Bytes is a utility library for working with bytes. From version 1.2.1 to before 1.11.1, Bytes is vulnerable to integer overflow in BytesMut::reserve. In the unique reclaim path of BytesMut::reserve, if the condition "v_capacity >= new_cap + offset" uses an unchecked addition. When new_cap + offset overflows usize in release builds, this condition may incorrectly pass, causing self.cap to be set to a value that exceeds the actual allocated capacity. Subsequent APIs such as spare_capacity_mut() then trust this corrupted cap value and may create out-of-bounds slices, leading to UB. This behavior is observable in release builds (integer overflow wraps), whereas debug builds panic due to overflow checks. This issue has been patched in version 1.11.1.
Bytes is a utility library for working with bytes. From version 1.2.1 ...