The remote SUSE Linux SLED15 / SLED_SAP15 / SLES15 / SLES_SAP15 / openSUSE 15 host has packages installed that are affected by a vulnerability as referenced in the SUSE-SU-2024:3404-1 advisory.

    - Update to version 0.10.0
    - CVE-2024-43806: Fixed rustix::fs::Dir iterator with the linux_raw backend that can cause memory     exhaustion. (bsc#1229959)

Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - 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. (CVE-2024-43806)

Note that Nessus relies on the presence of the package as reported by the vendor.

The version of flux / kata-containers / kata-containers-cc / rust / virtiofsd installed on the remote Azure Linux 3.0 host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the CVE-2024-43806 advisory.

  - 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. (CVE-2024-43806)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote SUSE Linux SLED15 / SLED_SAP15 / SLES15 / SLES_SAP15 host has a package installed that is affected by multiple vulnerabilities as referenced in the SUSE-SU-2026:3022-1 advisory.

    Update to version 0.15.0~17.

    - CVE-2023-26964: hyper,h2: high resource consumption due to stream stacking when H2 component processes       `HTTP2 RST_STREAM` frames (bsc#1210346).
    - CVE-2024-32650: rust-rustls: infinite loop in `rustls::conn::ConnectionCommon:complete_io()` when     processing client       input network input (bsc#1223238).
    - CVE-2025-3416: openssl: use-after-free in `Md::fetch` and `Cipher::fetch` (bsc#1242611).
    - CVE-2026-25727: time: stack exhaustion in the RFC 2822 date parser when processing certain user provided     input       (bsc#1257923).
    - CVE-2026-41676: openssl: short buffer overflow via `Deriver:derive` and `PkeyCtxRef:derive` when using     OpenSSL 1.1.1       (bsc#1270206).
    - CVE-2026-41677: openssl: out-of-bounds read in PEM password callback when returning an oversized length       (bsc#1270559).
    - CVE-2026-41678: openssl: OOB write due to incorrect bounds assertion in `aes::unwrap_key()`     (bsc#1270693).
    - CVE-2026-41681: openssl: stack corruption due to `MdCtxRef::digest_final()` writing past caller buffer     with no length       check (bsc#1270736).
    - CVE-2026-41898: openssl: information leak to network peers due to unchecked callback-returned length in     PSK and       cookie generate trampolines (bsc#1270869).
    - CVE-2026-42327: openssl: undefined behavior in `X509Ref::ocsp_responders` when processing certificates     with non-UTF-8       OCSP URLs (bsc#1270512).
    - CVE-2026-44662: openssl: heap buffer overflow when encrypting with AES key-wrap-with-padding     (bsc#1270938).
    - CVE-2026-45784: openssl: out-of-bounds write in `CipherCtxRef::cipher_update_inplace` for AES-KW-PAD     ciphers       (bsc#1270948).

Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of flux / kata-containers / kata-containers-cc / rust / virtiofsd installed on the remote CBL Mariner 2.0 host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the CVE-2024-43806 advisory.

  - 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. (CVE-2024-43806)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Published	Updated	Severity
207680	SUSE SLED15: rage-encryption / rage-encryption-bash-completion / etc (SUSE-SU-2024:3404-1)	Nessus	SuSE Local Security Checks	9/24/2024	6/25/2026	medium
228859	Linux Distros Unpatched Vulnerability : CVE-2024-43806	Nessus	Misc.	3/5/2025	7/25/2026	medium
216051	Azure Linux 3.0 Security Update: flux / kata-containers / kata-containers-cc / rust / virtiofsd (CVE-2024-43806)	Nessus	Azure Linux Local Security Checks	2/11/2025	1/22/2026	medium
327293	SUSE SLED15 / SLES15 Security Update : sccache (SUSE-SU-2026:3022-1)	Nessus	SuSE Local Security Checks	7/16/2026	7/20/2026	critical
213306	CBL Mariner 2.0 Security Update: flux / kata-containers / kata-containers-cc / rust / virtiofsd (CVE-2024-43806)	Nessus	MarinerOS Local Security Checks	12/21/2024	1/22/2026	medium

Detections

Analytics

Plugins Search

medium

medium

medium

critical

medium