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

  - crypto: algif_skcipher - force synchronous processing on trees without ctx->state The AIO/async path in     skcipher_recvmsg() passes the socket-wide ctx->iv directly into the skcipher request. After io_submit()     the socket lock is dropped and the request is processed asynchronously, so a concurrent     sendmsg(ALG_SET_IV) can overwrite ctx->iv and make the in-flight request run under an attacker-controlled     IV. For CTR/stream modes this is IV/keystream reuse and lets an unprivileged user recover the plaintext of     a concurrent operation. Snapshotting ctx->iv into per-request storage for the async path is not     sufficient. For ciphers with statesize == 0 - which includes cbc and ctr - the MSG_MORE inter-chunk IV     chaining is carried solely by the in-place req->iv writeback, which a snapshot redirects into per-request     memory that af_alg_free_resources() releases on completion, silently producing wrong output. Writing the     IV back from the completion callback instead is not possible either: that would require lock_sock() there,     but the callback can run in softirq/atomic context, so it must not sleep. Make the operation synchronous     instead, which removes both the IV race and any writeback race. This is equivalent to the upstream     resolution, commit fcc77d33a34c (net: Remove support for AIO on sockets), which removed the AIO socket     path across net/ entirely and so produces the same end state for this file. This patch deviates from that     commit deliberately: rather than removing AIO socket support tree-wide, which would be far too invasive     for stable, it removes only the AIO branch in crypto/algif_skcipher.c. io_submit() now completes     synchronously; AF_ALG async is rarely used in practice. The -EIOCBQUEUED check in skcipher_recvmsg() is     now dead but harmless, and is left alone to keep the fix minimal. Tested on 6.6.y: attacker IV injection     dropped from 2296/200000 to 0/200000 after the change; MSG_MORE chunked CTR output bit-identical to     single-shot. (CVE-2026-74578)

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

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2026-104542 advisory.

    In the Linux kernel, the following vulnerability has been resolved:

    crypto: algif_skcipher - force synchronous processing on trees without ctx->state

    The AIO/async path in skcipher_recvmsg() passes the socket-wide ctx->iv     directly into the skcipher request. After io_submit() the socket lock is     dropped and the request is processed asynchronously, so a concurrent     sendmsg(ALG_SET_IV) can overwrite ctx->iv and make the in-flight request     run under an attacker-controlled IV. For CTR/stream modes this is     IV/keystream reuse and lets an unprivileged user recover the plaintext of     a concurrent operation.

    Snapshotting ctx->iv into per-request storage for the async path is not     sufficient. For ciphers with statesize == 0 - which includes cbc and ctr -     the MSG_MORE inter-chunk IV chaining is carried solely by the in-place     req->iv writeback, which a snapshot redirects into per-request memory that     af_alg_free_resources() releases on completion, silently producing wrong     output. Writing the IV back from the completion callback instead is not     possible either: that would require lock_sock() there, but the callback can     run in softirq/atomic context, so it must not sleep.

    Make the operation synchronous instead, which removes both the IV race and     any writeback race. This is equivalent to the upstream resolution, commit     fcc77d33a34c (net: Remove support for AIO on sockets), which removed the     AIO socket path across net/ entirely and so produces the same end state for     this file. This patch deviates from that commit deliberately: rather than     removing AIO socket support tree-wide, which would be far too invasive for     stable, it removes only the AIO branch in crypto/algif_skcipher.c.
    io_submit() now completes synchronously; AF_ALG async is rarely used in     practice.

    The -EIOCBQUEUED check in skcipher_recvmsg() is now dead but harmless,     and is left alone to keep the fix minimal.

    Tested on 6.6.y: attacker IV injection dropped from 2296/200000 to 0/200000     after the change; MSG_MORE chunked CTR output bit-identical to single-shot.

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

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
337518	Linux Distros Unpatched Vulnerability : CVE-2026-74578	Nessus	Misc.	8/18/2026	8/28/2026	high
337224	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.10-2026-129 (ALASKERNEL-5.10-2026-129)	Nessus	Amazon Linux Local Security Checks	8/18/2026	9/7/2026	high
337239	Amazon Linux 2023 : bpftool6.12, kernel6.12, kernel6.12-devel (ALAS2023-2026-2057)	Nessus	Amazon Linux Local Security Checks	8/18/2026	9/7/2026	high
339536	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.15-2026-113 (ALASKERNEL-5.15-2026-113)	Nessus	Amazon Linux Local Security Checks	8/25/2026	9/4/2026	high
339569	Unity Linux 20.1050a Security Update: kernel (UTSA-2026-104542)	Nessus	Unity Linux Local Security Checks	8/26/2026	8/26/2026	high
337226	Amazon Linux 2023 : bpftool, kernel, kernel-devel (ALAS2023-2026-2058)	Nessus	Amazon Linux Local Security Checks	8/18/2026	9/7/2026	high
341880	Amazon Linux 2023 : bpftool6.18, kernel6.18, kernel6.18-devel (ALAS2023-2026-2071)	Nessus	Amazon Linux Local Security Checks	8/31/2026	9/7/2026	high

Detections

Analytics

Plugins Search

high

high

high

high

high

high

high