# CVE-2024-43806: rust-rustix: Rustix is a set of safe Rust bindings to POSIX-ish APIs

CVE-2024-43806 is fixed in 4 products on 1 platform, first by DEBIAN-CVE-2024-43806, released August 26, 2024. It is not reported as exploited. Patch Radar priority: Routine.

- Web page: https://patchblox.com/security/cve/CVE-2024-43806
- Priority: Routine
- CVSS: 6.5 (medium)
- EPSS: 0.0048
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: Aug 26, 2024

## Description

Rustix is a set of safe Rust bindings to POSIX-ish APIs. 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. The symptoms were initially discovered in https://github.com/imsnif/bandwhich/issues/284. That post has lots of details of our investigation. Full details can be read on the GHSA-c827-hfw6-qwvm repo advisory. 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. This issue has been addressed in release versions 0.35.15, 0.36.16, 0.37.25, and 0.38.19. Users are advised to upgrade. There are no known workarounds for this issue.

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | librsvg opensuse-leap 16.0 | 2.60.2-160000.1.1 | [OPENSUSE-SU-2026:20396-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-20396-1.md) | Mar 19, 2026 |
| Linux | librsvg sles 16.0 | 2.60.2-160000.1.1 | [SUSE-SU-2026:20910-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-20910-1.md) | Mar 19, 2026 |
| Linux | rage-encryption opensuse-leap 15.6 | 0.10.0+0-150500.3.6.1 | [SUSE-SU-2024:3404-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-3404-1.md) | Sep 23, 2024 |
| Linux | rage-encryption sles 15.6 | 0.10.0+0-150500.3.6.1 | [SUSE-SU-2024:3404-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-3404-1.md) | Sep 23, 2024 |
| Linux | rust-rustix Debian 13.5 (trixie) | 0.38.21-1 | [DEBIAN-CVE-2024-43806](https://patchblox.com/security/data/fix/linux/debian-cve-2024-43806.md) | Aug 26, 2024 |
| Linux | rust-rustix Debian 14 | 0.38.21-1 | [DEBIAN-CVE-2024-43806](https://patchblox.com/security/data/fix/linux/debian-cve-2024-43806.md) | Aug 26, 2024 |
| Linux | sccache sles 15.6 | 0.16.0~0-150600.10.11.1 | [SUSE-SU-2026:3022-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-3022-1.md) | Jul 15, 2026 |
| Linux | sccache sles 15.7 | 0.16.0~0-150600.10.11.1 | [SUSE-SU-2026:3022-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-3022-1.md) | Jul 15, 2026 |

---

Data as of 2026-11-09T07:25:28Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.