Skip to main content
Public proof of conceptFix available

CVE-2024-43806

A public proof of concept exists; no exploitation attested.

  • Published2024-08-26
  • Fixed in0.38.19 · 0.37.25 · 0.36.16 · 0.35.15
  • WeaknessCWE-400

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2024-08-2619:15CVE publishedNVD

Versions per branch

CISA-ADP · OSV
Bytecodealliance rustix
BranchAffectedFixed in
0.38≥ 0.38.0, < 0.38.190.38.19
0.37≥ 0.37.0, < 0.37.250.37.25
0.36≥ 0.36.0, < 0.36.160.36.16
0.35≥ 0.35.11, < 0.35.150.35.15

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • bytecodealliance rustix
    Affected
    • = >= 0.35.11, < 0.35.15no fix stated
    • = >= 0.36.0, < 0.36.16no fix stated
    • = >= 0.37.0, < 0.37.25no fix stated
    • = >= 0.38.0, < 0.38.19no fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2024-08-26

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • 389-dsopenSUSE:Tumbleweedall versions · fixed in 3.1.1~git13.a9c7ff9-1.1
  • batWolfiall versions · fixed in 0.24.0-r2and 1 other package
  • batChainguardall versions · fixed in 0.24.0-r2and 1 other package
  • bergWolfiall versions · fixed in 0.3.5-r2
  • bergChainguardall versions · fixed in 0.3.5-r2
  • cloud-hypervisorAzure Linux:2all versions · fixed in 32.0-7
  • fluxAzure Linux:3all versions · fixed in 0.194.5-4
  • kata-containersAzure Linux:3all versions · fixed in 3.2.0.azl4-1and 1 other package

38 more package ranges on OSV.dev

Full record on NVD

Fix

  1. Update Bytecodealliance rustix to 0.38.19 · 0.37.25 · 0.36.16 · 0.35.15

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • NVDCVE recordread 2026-10-23
  • CISA-ADPSSVC decisionpoc2024-08-26
  • CNACVSS 3.16.5known since 2026-10-23
  • CNAweakness (CWE)CWE-400known since 2026-10-23
  • FIRST EPSSEPSS score0.5 %2026-11-08
  • OSVaffected packages—
  • GitHub AdvisoriesadvisoryMODERATE2023-10-18

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Published
2024-08-26
Last Modified
2026-06-17
NVD status
Deferred
GitHub Advisory
GHSA-c827-hfw6-qwvm

Frequently asked questions

What is CVE-2024-43806?

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.

Is CVE-2024-43806 actively exploited?

A proof-of-concept exploit exists for CVE-2024-43806, but active exploitation has not been confirmed at this time.

What is the CVSS score for CVE-2024-43806?

CVE-2024-43806 has a CVSS v3 base score of 6.5 (MEDIUM severity), with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.

Running rustix? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record