cve.bz

CVE-2026-74578 linux linux

7.1 highEPSS 0.1%Fix available

High (7.1) in linux linux. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

7.1 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
EPSS
0.1% (unchanged from 0.1% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 4th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • Linux Linux: fixed in 5.10.261
  • Linux Linux: fixed in 5.15.212
  • Linux Linux: fixed in 6.1.178
  • Linux Linux: fixed in 6.6.145
  • Linux Linux: fixed in 6.12.97
  • Linux Linux: fixed in 6.18.40
  • Linux Linux: fixed in 7.1.5
  • Linux Linux: fixed in 7.2
  • Debian, Ubuntu, SUSE, openSUSE, Alpaquita: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2026-74578 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-74578?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-74578?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-74578 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux4.14 and later

Fixed in

ProductRelease lineFixed in
Linux5.105.10.261
Linux5.155.15.212
Linux6.16.1.178
Linux6.66.6.145
Linux6.126.12.97
Linux6.186.18.40
Linux7.17.1.5
Linuxlater releases7.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux6.1.180-1DEBIAN-CVE-2026-74578
Debian13linux6.12.100-1DEBIAN-CVE-2026-74578
Debian14linux7.1.5-1DEBIAN-CVE-2026-74578
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-74578
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-74578
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-74578
Ubuntu22.04:LTSlinux5.15.0-198.208UBUNTU-CVE-2026-74578 USN-8875-1
Ubuntu22.04:LTSlinux-aws5.15.0-1117.124UBUNTU-CVE-2026-74578 USN-8875-1
Ubuntu22.04:LTSlinux-azure5.15.0-1123.132UBUNTU-CVE-2026-74578 USN-8875-1
Ubuntu22.04:LTSlinux-azure-fde5.15.0-1122.131UBUNTU-CVE-2026-74578 USN-8876-1
Ubuntu22.04:LTSlinux-gcp5.15.0-1118.128UBUNTU-CVE-2026-74578 USN-8877-1
Ubuntu22.04:LTSlinux-gke5.15.0-1113.119UBUNTU-CVE-2026-74578 USN-8875-1
Ubuntu22.04:LTSlinux-gkeop5.15.0-1100.108UBUNTU-CVE-2026-74578 USN-8875-1
Ubuntu22.04:LTSlinux-ibm5.15.0-1111.115UBUNTU-CVE-2026-74578 USN-8875-1
Ubuntu22.04:LTSlinux-intel-iotg5.15.0-1112.118UBUNTU-CVE-2026-74578 USN-8875-1
37 more for Ubuntu in the JSON and on Ubuntu's page.
SUSELinux Enterprise High Availability Extension 15 SP4, Linux Enterprise Live Patching 15 SP4kernel-default5.14.21-150400.24.246.1SUSE-SU-2026:4937-1
SUSELinux Enterprise High Availability Extension 15 SP6, Linux Enterprise Live Patching 15 SP6kernel-default6.4.0-150600.23.143.1SUSE-SU-2026:4934-1
SUSELinux Enterprise High Availability Extension 15 SP7, Linux Enterprise Live Patching 15 SP7, Linux Enterprise Module for Legacy 15 SP7 and 1 morekernel-default6.4.0-150700.53.87.3SUSE-SU-2026:4935-1
SUSELinux Enterprise High Availability Extension 16.0kernel-default6.12.0-160000.40.1SUSE-SU-2026:24437-1
SUSELinux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSSkernel-64kb, kernel-docs, kernel-syms and 3 more5.14.21-150400.24.246.1SUSE-SU-2026:4937-1
SUSELinux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSS, Linux Enterprise Micro 5.3 and 3 morekernel-default-base5.14.21-150400.24.246.1.150400.24.124.1SUSE-SU-2026:4937-1
SUSELinux Enterprise High Performance Computing 15 SP5-ESPOS, Linux Enterprise High Performance Computing 15 SP5-LTSSkernel-64kb, kernel-docs, kernel-syms and 3 more5.14.21-150500.55.195.1SUSE-SU-2026:4936-1
SUSELinux Enterprise High Performance Computing 15 SP5-ESPOS, Linux Enterprise High Performance Computing 15 SP5-LTSS, Linux Enterprise Micro 5.5 and 2 morekernel-default-base5.14.21-150500.55.195.1.150500.6.91.1SUSE-SU-2026:4936-1
SUSELinux Enterprise Live Patching 12 SP5kernel-default4.12.14-122.336.1SUSE-SU-2026:4892-1
SUSELinux Enterprise Live Patching 12 SP5kgraft-patch-SLE12-SP5_Update_891-8.3.1SUSE-SU-2026:4892-1
SUSELinux Enterprise Live Patching 15 SP4kernel-livepatch-SLE15-SP4_Update_611-150400.9.3.1SUSE-SU-2026:4937-1
SUSELinux Enterprise Live Patching 15 SP5kernel-default5.14.21-150500.55.195.1SUSE-SU-2026:4936-1
35 more for SUSE in the JSON and on SUSE's page.
openSUSELeap 16.0kernel-default-base6.12.0-160000.40.1.160000.2.29openSUSE-SU-2026:22167-1
openSUSELeap 16.0kernel-rt, dtb-aarch64, kernel-64kb and 9 more6.12.0-160000.40.1openSUSE-SU-2026:22167-1
openSUSELeap 16.1kernel-default-base6.12.0-160100.9.1.160100.3.14openSUSE-SU-2026:22309-1
openSUSELeap 16.1kernel-nvidia64kb, kernel-syms-nvidia, kernel-source-nvidia6.12.0-160100.6.1openSUSE-SU-2026:22313-1
openSUSELeap 16.1kernel-rt, dtb-aarch64, kernel-64kb and 9 more6.12.0-160100.9.1openSUSE-SU-2026:22309-1
Alpaquita23linux-lts6.1.182-r0BELL-CVE-2026-74578
Alpaquita25linux-lts6.12.103-r0BELL-CVE-2026-74578
Alpaquitastreamlinux-lts6.18.43-r0BELL-CVE-2026-74578

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A race in crypto algif_skcipher allows the async skcipher_recvmsg() path to pass the socket wide ctx iv directly into an in flight skcipher request. After io_submit() the socket lock can be dropped while the request is still processed, so a concurrent sendmsg(ALG_SET_IV) can replace ctx iv and make the operation run with attacker controlled IV material. For CTR and stream like modes this can cause IV or keystream reuse and may allow recovery of plaintext from a concurrent operation. For the CVSS the PR:L is used because triggering requires a local process that can use AF_ALG sockets and submit the racing operations, but no administrative privileges are required in typical configurations. The issue is not network reachable by itself and affects local crypto API users. Impact is mainly confidentiality loss and possible integrity impact through attacker controlled IV selection, not kernel code execution or a direct privilege escalation.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelAffected
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelAffected
Red Hat Enterprise Linux 8kernel-rtAffected
Red Hat Enterprise Linux 9kernelAffected
Red Hat Enterprise Linux 9kernel-rtAffected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-74578.

References

Check your stackJSON