rustix

Activity

Latest release: 6mo ago
Total releases: 169
Cadence: ~7 days
Last 12 months: 2

Details

License: Apache-2.0 WITH LLVM-exception OR Apache-2.0 OR MIT
First release: Oct 29, 2021

Releases

Version	Released
`1.1.4` unknown	Feb 22, 2026
`1.1.3` unknown	Dec 23, 2025
`1.1.2` unknown	Sep 09, 2025
`1.1.1` unknown	Sep 09, 2025
`1.1.0` unknown yanked	Sep 09, 2025
`1.0.8` unknown	Jul 15, 2025
`1.0.7` unknown	Apr 30, 2025
`1.0.6` unknown	Apr 30, 2025
`1.0.5` unknown	Apr 01, 2025
`1.0.4` unknown	Apr 01, 2025
`1.0.3` unknown	Mar 18, 2025
`1.0.2` unknown	Mar 10, 2025
`1.0.1` unknown	Mar 07, 2025
`1.0.0` unknown	Mar 06, 2025
`1.0.0-prerelease.1` unknown	Feb 26, 2025
`1.0.0-prerelease.0` unknown	Feb 15, 2025
`0.38.44` unknown	Jan 21, 2025
`0.37.28` unknown	Jan 07, 2025
`0.38.43` unknown	Jan 07, 2025
`0.38.42` unknown	Dec 09, 2024
`0.38.41` unknown	Nov 18, 2024
`0.38.40` unknown	Nov 10, 2024
`0.38.39` unknown	Nov 04, 2024
`0.38.38` unknown	Oct 27, 2024
`0.38.37` unknown	Sep 11, 2024
`0.38.36` unknown	Sep 05, 2024
`0.38.35` unknown	Aug 27, 2024
`0.38.34` unknown	Apr 22, 2024
`0.38.33` unknown yanked	Apr 21, 2024
`0.38.32` unknown	Mar 19, 2024
`0.38.31` unknown	Feb 01, 2024
`0.38.30` unknown	Jan 12, 2024
`0.38.29` unknown yanked	Jan 12, 2024
`0.38.28` unknown	Dec 09, 2023
`0.38.27` unknown	Dec 08, 2023
`0.38.26` unknown	Dec 01, 2023
`0.38.25` unknown	Nov 19, 2023
`0.38.24` unknown	Nov 15, 2023
`0.38.23` unknown	Nov 14, 2023
`0.38.22` unknown yanked	Nov 13, 2023
`0.35.16` unknown	Oct 26, 2023
`0.36.17` unknown	Oct 26, 2023
`0.37.27` unknown	Oct 26, 2023
`0.38.21` unknown	Oct 26, 2023
`0.38.20` unknown	Oct 19, 2023
`0.37.26` unknown	Oct 19, 2023
`0.35.15` unknown	Oct 12, 2023
`0.36.16` unknown	Oct 12, 2023
`0.37.25` unknown	Oct 12, 2023
`0.38.19` unknown	Oct 12, 2023

1–50 of 169

Dependencies (16)

Depends on

1.1.4

Used by

1131

Supply-chain exposure

1,131 tracked projects depend on this, <1% of every package we track.

A known CVE here directly exposes every one of them.

Known CVEs (1)

CVE-2024-43806 GHSA-c827-hfw6-qwvm Oct 18, 2023

rustix's `rustix::fs::Dir` iterator with the `linux_raw` backend can cause memory explosion

6.5 / 10
Medium
Network Low Low None Unchanged None None High

Summary

When using rustix::fs::Dir using the linux_raw backend, it's possible for the iterator to "get stuck" when an IO error is encountered. Combined with a memory over-allocation issue in rustix::fs::Dir::read_more, this can cause quick and unbounded memory explosion (gigabytes in a few seconds if used on a hot path) and eventually lead to an OOM crash of the application.

Details

Discovery

The symptoms were initially discovered in https://github.com/imsnif/bandwhich/issues/284. That post has lots of details of our investigation. See this post and the Discord thread for details.

Diagnosis

This issue is caused by the combination of two independent bugs:

Stuck iterator

The rustix::fs::Dir iterator can fail to halt after encountering an IO error, causing the caller to be stuck in an infinite loop.

Memory over-allocation

Dir::read_more incorrectly grows the read buffer unconditionally each time it is called, regardless of necessity.

Since <Dir as Iterator>::next calls Dir::read, which in turn calls Dir::read_more, this means an IO error encountered during reading a directory can lead to rapid and unbounded growth of memory use.

PoC

fn main() -> Result<(), Box<dyn std::error::Error>> { // create a directory, get a FD to it, then unlink the directory but keep the FD std::fs::create_dir("tmp_dir")?; let dir_fd = rustix::fs::openat( rustix::fs::CWD, rustix::cstr!("tmp_dir"), rustix::fs::OFlags::RDONLY | rustix::fs::OFlags::CLOEXEC, rustix::fs::Mode::empty(), )?; std::fs::remove_dir("tmp_dir")?; // iterator gets stuck in infinite loop and memory explodes rustix::fs::Dir::read_from(dir_fd)? // the iterator keeps returning `Some(Err(_))`, but never halts by returning `None` // therefore if the implementation ignores the error (or otherwise continues // after seeing the error instead of breaking), the loop will not halt .filter_map(|dirent_maybe_error| dirent_maybe_error.ok()) .for_each(|dirent| { // your happy path println!("{dirent:?}"); }); Ok(()) }

Impact

If a program tries to access a directory with its file descriptor after the file has been unlinked (or any other action that leaves the Dir iterator in the stuck state), and the implementation does not break after seeing an error, it can cause a memory explosion.

As an example, Linux's various virtual file systems (e.g. /proc, /sys) can contain directories that spontaneously pop in and out of existence. Attempting to iterate over them using rustix::fs::Dir directly or indirectly (e.g. with the procfs crate) can trigger this fault condition if the implementation decides to continue on errors.

An attacker knowledgeable about the implementation details of a vulnerable target can therefore try to trigger this fault condition via any one or a combination of several available APIs. If successful, the application host will quickly run out of memory, after which the application will likely be terminated by an OOM killer, leading to denial of service.

Fixed in

0.35.150.36.160.37.250.38.19

References

https://github.com/bytecodealliance/rustix/security/advisories/GHSA-c827-hfw6-qwvm
https://nvd.nist.gov/vuln/detail/CVE-2024-43806
https://github.com/imsnif/bandwhich/issues/284
https://github.com/imsnif/bandwhich/issues/284#issuecomment-1754321993
https://github.com/bytecodealliance/rustix/commit/31fd98ca723b93cc6101a3e29843ea5cf094e159
https://github.com/bytecodealliance/rustix/commit/87481a97f4364d12d5d6f30cdd025a0fc509b8ec

Updated Sep 10, 2026 · Source: OSV.dev

Insights

Releases per month

last 12 months

Release mix

unknown 169

169 releases

Dependencies over time

per release

Release calendar

2026

Jan

Feb

Mar

Apr

May

Jun

Jul

Aug

Sep

Oct

Nov

Dec

Less More