CVE-2024-43806: `rustix::fs::Dir` iterator with the `linux_raw` backend can cause memory explosion
Noroxi assessment
Priority: Monitor (action score 26/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.48% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: azl3 flux 0.194.5-2 on Azure Linux 3.0 0.194.5-2; azl3 flux 0.194.5-4 on Azure Linux 3.0 0.194.5-2; azl3 kata-containers 3.2.0.azl3-2 on Azure Linux 3.0 3.2.0.azl4-1.
Low priority for now. Upgrade to azl3 flux 0.194.5-2 on Azure Linux 3.0 0.194.5-2; azl3 flux 0.194.5-4 on Azure Linux 3.0 0.194.5-2; azl3 kata-containers 3.2.0.azl3-2 on Azure Linux 3.0 3.2.0.azl4-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- GHSA-c827-hfw6-qwvm
- openSUSE-SU-2024:14306-1
- openSUSE-SU-2024:14354-1
- openSUSE-SU-2025:15294-1
- openSUSE-SU-2026:20396-1
- SUSE-SU-2024:3404-1
- SUSE-SU-2025:02809-1
- SUSE-SU-2025:02810-1
- SUSE-SU-2025:02811-1
- SUSE-SU-2025:20057-1
- SUSE-SU-2025:20858-1
- SUSE-SU-2025:4411-1
- SUSE-SU-2026:20755-1
- SUSE-SU-2026:20910-1
- SUSE-SU-2026:3022-1
- Published
- Aug 26, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.4% · 41th percentile
- CWE
- CWE-400
Report tools
Action score
26
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 6.5
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| bytecodealliance | rustix | cpe:2.3:a:bytecodealliance:rustix |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
bytecodealliance rustix
- >= 0.35.11, < 0.35.15, >= 0.36.0, < 0.36.16, >= 0.37.0, < 0.37.25, >= 0.38.0, < 0.38.19affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| crates.io | rustix | from 0.35.11 · before 0.35.15 | 0.35.15 |
| crates.io | rustix | from 0.36.0 · before 0.36.16 | 0.36.16 |
| crates.io | rustix | from 0.37.0 · before 0.37.25 | 0.37.25 |
| crates.io | rustix | from 0.38.0 · before 0.38.19 | 0.38.19 |
| Debian:12 | rust-rustix | from 0 | — |
| Debian:13 | rust-rustix | before 0.38.21-1 | 0.38.21-1 |
| openSUSE:Leap 15.5 | rage-encryption | before 0.10.0+0-150500.3.6.1 | 0.10.0+0-150500.3.6.1 |
| openSUSE:Leap 16.0 | librsvg | before 2.60.2-160000.1.1 | 2.60.2-160000.1.1 |
| openSUSE:Tumbleweed | 389-ds | before 3.1.1~git13.a9c7ff9-1.1 | 3.1.1~git13.a9c7ff9-1.1 |
| openSUSE:Tumbleweed | rage-encryption | before 0.10.0+0-3.1 | 0.10.0+0-3.1 |
| openSUSE:Tumbleweed | rust-keylime | before 0.2.7+70-2.1 | 0.2.7+70-2.1 |
| SUSE:Linux Enterprise Micro 5.3 | librsvg | before 2.52.12-150400.3.9.1 | 2.52.12-150400.3.9.1 |
| SUSE:Linux Enterprise Micro 5.3 | rust-keylime | before 0.2.7+141-150400.3.7.1 | 0.2.7+141-150400.3.7.1 |
| SUSE:Linux Enterprise Micro 5.4 | rust-keylime | before 0.2.7+141-150400.3.5.1 | 0.2.7+141-150400.3.5.1 |
| SUSE:Linux Enterprise Micro 5.5 | rust-keylime | before 0.2.7+141-150500.3.5.1 | 0.2.7+141-150500.3.5.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP5 | rage-encryption | before 0.10.0+0-150500.3.6.1 | 0.10.0+0-150500.3.6.1 |
| SUSE:Linux Enterprise Module for Development Tools 15 SP7 | sccache | before 0.16.0~0-150600.10.11.1 | 0.16.0~0-150600.10.11.1 |
| SUSE:Linux Micro 6.0 | rust-keylime | before 0.2.6+13-1.1 | 0.2.6+13-1.1 |
| SUSE:Linux Micro 6.1 | rust-keylime | before 0.2.8+12-slfo.1.1_1.1 | 0.2.8+12-slfo.1.1_1.1 |
| SUSE:Linux Micro 6.2 | librsvg | before 2.60.2-160000.1.1 | 2.60.2-160000.1.1 |
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| azl3 flux 0.194.5-2 on Azure Linux 3.0 | 0.194.5-2 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 flux 0.194.5-4 on Azure Linux 3.0 | 0.194.5-2 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 kata-containers 3.2.0.azl3-2 on Azure Linux 3.0 | 3.2.0.azl4-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 kata-containers 3.2.0.azl4-1 on Azure Linux 3.0 | 3.2.0.azl4-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 kata-containers-cc 3.2.0.azl3-1 on Azure Linux 3.0 | 3.2.0.azl4-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 kata-containers-cc 3.2.0.azl4-1 on Azure Linux 3.0 | 3.2.0.azl4-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 virtiofsd 1.8.0-3 on Azure Linux 3.0 | 1.8.0-3 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 cloud-hypervisor 32.0-7 on CBL Mariner 2.0 | 32.0-7 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 cloud-hypervisor 32.0-7 on CBL-Mariner 2.0 | 32.0-7 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kata-containers-cc 3.2.0.azl2-7 on CBL Mariner 2.0 | 3.2.0.azl2-7 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kata-containers-cc 3.2.0.azl2-7 on CBL-Mariner 2.0 | 3.2.0.azl2-7 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 rust 1.72.0-10 on CBL Mariner 2.0 | 1.72.0-9 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 rust 1.72.0-10 on CBL-Mariner 2.0 | 1.72.0-9 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 rust 1.72.0-9 on CBL Mariner 2.0 | 1.72.0-9 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 virtiofsd 1.8.0-3 on CBL Mariner 2.0 | 1.8.0-3 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 virtiofsd 1.8.0-3 on CBL-Mariner 2.0 | 1.8.0-3 · CBL-Mariner Releases | Microsoft (MSRC) |
| crates.io:rustix | 0.35.15 | Package registry (OSV) |
| crates.io:rustix | 0.36.16 | Package registry (OSV) |
| crates.io:rustix | 0.37.25 | Package registry (OSV) |
| crates.io:rustix | 0.38.19 | Package registry (OSV) |
| debian:rust-rustix | 0.38.21-1 · Debian:13 | Package registry (OSV) |
| opensuse:389-ds | 3.1.1~git13.a9c7ff9-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:librsvg | 2.60.2-160000.1.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:rage-encryption | 0.10.0+0-150500.3.6.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:rust-keylime | 0.2.7+70-2.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| suse:librsvg | 2.52.12-150400.3.9.1 · SUSE:Linux Enterprise Micro 5.3 | Package registry (OSV) |
| suse:rage-encryption | 0.10.0+0-150500.3.6.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP5 | Package registry (OSV) |
| suse:rust-keylime | 0.2.7+141-150400.3.7.1 · SUSE:Linux Enterprise Micro 5.3 | Package registry (OSV) |
| suse:sccache | 0.16.0~0-150600.10.11.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP7 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-400 · Uncontrolled Resource ConsumptionCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-secondary
Root cause
Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.
The bug in code
The whole CWE-400 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
function expand(node) {
return node.children.map(expand);
}Fixed
const MAX_DEPTH = 32;
function expand(node, depth = 0) {
if (depth > MAX_DEPTH) throw new Error("too deep");
return node.children.map((c) => expand(c, depth + 1));
}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.