CVE-2024-43806

MEDIUMNVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.5% (39th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 6.5Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
45
EG Risk 45/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
39th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 26, 2024

Last Modified

April 15, 2026

References (2)

Vendor Advisories for CVE-2024-43806(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 4 ecosystems)
crates.io(1)
PackageVulnerable rangeFix by version rangeDependents
rustix—
  • 0.35.11 up to 0.35.15: fixed in 0.35.15
  • 0.36.0 up to 0.36.16: fixed in 0.36.16
  • 0.37.0 up to 0.37.25: fixed in 0.37.25
  • 0.38.0 up to 0.38.19: fixed in 0.38.19
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
rust-rustix0.35.12-1 ... 1.1.4+dfsg-1 (23 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
rust-rustix—
  • every version up to 0.38.21-1: fixed in 0.38.21-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
rust-rustix—
  • every version up to 0.38.21-1: fixed in 0.38.21-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 32× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 196 total refreshes for this CVE.

  1. 2026-10-10 19:58 UTCEPSS rescore
  2. 2026-10-09 20:05 UTCEPSS rescore
  3. 2026-10-08 17:08 UTCEPSS rescore
  4. 2026-10-07 23:46 UTCEPSS rescore
  5. 2026-10-07 09:05 UTCOSV refresh
  6. 2026-10-06 15:15 UTCEPSS rescore
  7. 2026-10-05 17:41 UTCEPSS rescore
  8. 2026-10-04 23:20 UTCEPSS rescore
  9. 2026-10-03 14:24 UTCEPSS rescore
  10. 2026-10-01 19:48 UTCEPSS rescore
  11. 2026-09-30 19:52 UTCEG score recompute
  12. 2026-09-30 15:01 UTCEPSS rescore
  13. 2026-09-29 15:17 UTCEPSS rescore
  14. 2026-09-28 13:50 UTCEPSS rescore
  15. 2026-09-27 13:44 UTCEPSS rescore
  16. 2026-09-26 15:57 UTCEPSS rescore
  17. 2026-09-24 14:01 UTCEPSS rescore
  18. 2026-09-23 13:46 UTCEPSS rescore
  19. 2026-09-22 14:47 UTCEPSS rescore
  20. 2026-09-21 20:32 UTCEPSS rescore
  21. 2026-09-19 15:40 UTCEPSS rescore
  22. 2026-09-18 19:26 UTCEPSS rescore
  23. 2026-09-18 19:26 UTCEPSS rescore
  24. 2026-09-17 14:50 UTCOSV refresh
  25. 2026-09-16 14:06 UTCEPSS rescore
Show 75 more
  1. 2026-09-16 05:12 UTCEPSS rescore
  2. 2026-09-15 03:08 UTCEPSS rescore
  3. 2026-09-15 03:08 UTCEPSS rescore
  4. 2026-09-13 16:45 UTCEPSS rescore
  5. 2026-09-12 14:59 UTCEPSS rescore
  6. 2026-09-11 14:51 UTCEPSS rescore
  7. 2026-09-11 09:35 UTCEPSS rescore
  8. 2026-09-08 21:58 UTCEPSS rescore
  9. 2026-09-07 16:00 UTCEPSS rescore
  10. 2026-09-06 13:46 UTCEPSS rescore
  11. 2026-09-06 13:46 UTCEPSS rescore
  12. 2026-09-05 15:27 UTCEPSS rescore
  13. 2026-09-04 13:59 UTCEPSS rescore
  14. 2026-09-04 05:05 UTCEPSS rescore
  15. 2026-09-02 14:10 UTCEPSS rescore
  16. 2026-09-01 13:52 UTCEPSS rescore
  17. 2026-08-30 19:16 UTCEPSS rescore
  18. 2026-08-29 15:13 UTCOSV refresh
  19. 2026-08-28 21:39 UTCEPSS rescore
  20. 2026-08-27 14:23 UTCEPSS rescore
  21. 2026-08-25 13:47 UTCEPSS rescore
  22. 2026-08-24 14:15 UTCEPSS rescore
  23. 2026-08-23 00:18 UTCEPSS rescore
  24. 2026-08-21 23:47 UTCEPSS rescore
  25. 2026-08-20 22:54 UTCEPSS rescore
  26. 2026-08-19 17:02 UTCEPSS rescore
  27. 2026-08-18 13:46 UTCEPSS rescore
  28. 2026-08-17 13:45 UTCEPSS rescore
  29. 2026-08-16 14:54 UTCEPSS rescore
  30. 2026-08-16 02:13 UTCEPSS rescore
  31. 2026-08-15 01:28 UTCEPSS rescore
  32. 2026-08-13 21:59 UTCEPSS rescore
  33. 2026-08-13 02:43 UTCOSV refresh
  34. 2026-08-12 13:49 UTCEPSS rescore
  35. 2026-08-11 13:40 UTCEPSS rescore
  36. 2026-08-10 23:58 UTCEPSS rescore
  37. 2026-08-09 13:45 UTCEPSS rescore
  38. 2026-08-07 16:25 UTCEPSS rescore
  39. 2026-08-06 13:45 UTCEPSS rescore
  40. 2026-08-05 19:16 UTCEPSS rescore
  41. 2026-08-04 15:08 UTCEPSS rescore
  42. 2026-08-04 10:36 UTCEPSS rescore
  43. 2026-08-03 10:34 UTCEPSS rescore
  44. 2026-08-02 02:25 UTCEPSS rescore
  45. 2026-08-01 04:14 UTCEPSS rescore
  46. 2026-07-30 16:26 UTCEPSS rescore
  47. 2026-07-30 01:29 UTCEPSS rescore
  48. 2026-07-28 15:34 UTCEPSS rescore
  49. 2026-07-28 10:54 UTCOSV refresh
  50. 2026-07-27 14:11 UTCEPSS rescore
  51. 2026-07-26 14:53 UTCEPSS rescore
  52. 2026-07-26 14:53 UTCEPSS rescore
  53. 2026-07-25 14:16 UTCEPSS rescore
  54. 2026-07-24 14:16 UTCEPSS rescore
  55. 2026-07-23 14:17 UTCEPSS rescore
  56. 2026-07-23 02:40 UTCEG score recompute
  57. 2026-07-22 14:07 UTCEPSS rescore
  58. 2026-07-21 15:23 UTCEPSS rescore
  59. 2026-07-21 15:23 UTCEPSS rescore
  60. 2026-07-20 17:06 UTCEPSS rescore
  61. 2026-07-19 14:30 UTCEPSS rescore
  62. 2026-07-19 14:30 UTCEPSS rescore
  63. 2026-07-19 02:28 UTCEPSS rescore
  64. 2026-07-19 02:28 UTCEPSS rescore
  65. 2026-07-18 10:03 UTCEPSS rescore
  66. 2026-07-18 10:03 UTCEPSS rescore
  67. 2026-07-16 17:02 UTCEPSS rescore
  68. 2026-07-15 16:56 UTCEPSS rescore
  69. 2026-07-15 16:56 UTCEPSS rescore
  70. 2026-07-15 01:59 UTCEPSS rescore
  71. 2026-07-15 01:59 UTCEPSS rescore
  72. 2026-07-13 22:29 UTCEPSS rescore
  73. 2026-07-13 06:12 UTCEPSS rescore
  74. 2026-07-12 05:45 UTCEPSS rescore
  75. 2026-07-12 05:45 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2024-43806?
CVE-2024-43806 is a medium vulnerability published on August 26, 2024. Rustix is a set of safe Rust bindings to POSIX-ish APIs. When using rustix::fs::Dir using the linuxraw 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::readmore, this can cause quick and…
When was CVE-2024-43806 disclosed?
CVE-2024-43806 was first published on August 26, 2024, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-43806 actively exploited?
CVE-2024-43806 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-43806?
CVE-2024-43806 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2024-43806?
A fix for CVE-2024-43806 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-43806 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-43806

Explore →

Is Your Infrastructure Affected by CVE-2024-43806?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs