Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

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…

Historical advisory saved 2 Nov 2026 22:59:18 UTC. The publisher may have updated it since then. Latest advisory.

euvd · EUVD-2023-2715

Published

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.

Additional publisher context

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Aug 26, 2024, 6:43:22 PM

dateUpdated: Aug 26, 2024, 7:40:46 PM

14 related source bulletins · separate from aliases

SUSE-SU-2025:02809-1: Security update for rust-keylime

CVE-2023-26964 · CVE-2024-12224 · CVE-2024-32650 · CVE-2024-43806 · CVE-2025-3416 · CVE-2025-58266

SUSE-SU-2025:02810-1: Security update for rust-keylime

CVE-2023-26964 · CVE-2024-12224 · CVE-2024-32650 · CVE-2024-43806 · CVE-2025-3416 · CVE-2025-58266

SUSE-SU-2024:3404-1: Security update for rage-encryption

CVE-2024-43806

openSUSE-SU-2024:14354-1: rage-encryption-0.10.0+0-3.1 on GA media

CVE-2024-43806

SUSE-SU-2025:4411-1: Security update for librsvg

CVE-2024-12224 · CVE-2024-43806

SUSE-SU-2025:20858-1: Security update for rust-keylime

CVE-2024-12224 · CVE-2024-43806 · CVE-2024-58266 · CVE-2025-3416 · CVE-2025-55159

openSUSE-SU-2025:15294-1: keylime-ima-policy-0.2.7+70-2.1 on GA media

CVE-2024-12224 · CVE-2024-43806

openSUSE-SU-2026:20396-1: Security update for librsvg

CVE-2024-12224 · CVE-2024-43806

openSUSE-SU-2024:14306-1: 389-ds-3.1.1~git13.a9c7ff9-1.1 on GA media

CVE-2024-43806

SUSE-SU-2025:20057-1: Security update for rust-keylime

CVE-2024-32650 · CVE-2024-43806

msrc_CVE-2024-43806: `rustix::fs::Dir` iterator with the `linux_raw` backend can cause memory explosion

CVE-2024-43806

SUSE-SU-2025:02811-1: Security update for rust-keylime

CVE-2023-26964 · CVE-2024-12224 · CVE-2024-32650 · CVE-2024-43806 · CVE-2025-3416 · CVE-2025-58266

SUSE-SU-2026:20910-1: Security update for librsvg

CVE-2024-12224 · CVE-2024-43806

SUSE-SU-2026:20755-1: Security update for librsvg

CVE-2024-12224 · CVE-2024-43806

Source published
Aug 26, 2024, 6:43:22 PM (timezone not stated)
Source modified
Aug 26, 2024, 7:40:46 PM (timezone not stated)
Saved here
2 Nov 2026 22:59:18 UTC
Source terms
ENISA EUVD · source terms and attribution apply

Original source record · Cite this exact observation · Complete original publisher JSON

Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

EUVD CVSS 3.1 · 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 21:28 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current