CVE-2026-74466 linux linux
linux linux: no CVSS score yet. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
On this page
- EPSS
- 0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 8th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
- Published
- Modified
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Fix and patched versions
- Linux Linux: fixed in 6.1.191
- Linux Linux: fixed in 6.6.160
- Linux Linux: fixed in 6.12.114
- Linux Linux: fixed in 6.18.57
- Linux Linux: fixed in 7.1.8
- Linux Linux: fixed in 7.2
- Debian, Ubuntu, SUSE, openSUSE, Alpaquita: fixed package versions per release
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-74466 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-74466?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-74466?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-74466 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.
| Product | Affected |
|---|---|
| Linux | 5.18 and later |
Fixed in
| Product | Release line | Fixed in |
|---|---|---|
| Linux | 6.1 | 6.1.191 |
| Linux | 6.6 | 6.6.160 |
| Linux | 6.12 | 6.12.114 |
| Linux | 6.18 | 6.18.57 |
| Linux | 7.1 | 7.1.8 |
| Linux | later releases | 7.2 |
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12 | linux | no fix listed | DEBIAN-CVE-2026-74466 |
| Debian | 12 | linux-6.12 | 6.12.115-2~deb12u1 | DEBIAN-CVE-2026-74466 |
| Debian | 13 | linux | 6.12.115-2 | DEBIAN-CVE-2026-74466 |
| Debian | 14 | linux | 7.1.8-1 | DEBIAN-CVE-2026-74466 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2026-74466 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2026-74466 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2026-74466 |
| Ubuntu | 22.04:LTS | linux-riscv, linux-aws-6.2, linux-aws-6.5 and 40 more | no fix listed | UBUNTU-CVE-2026-74466 |
| Ubuntu | 24.04:LTS | linux, linux-aws, linux-gcp and 44 more | no fix listed | UBUNTU-CVE-2026-74466 |
| Ubuntu | 24.04:LTS | linux-aws-7.0 | 7.0.0-1017.18~24.04.1 | UBUNTU-CVE-2026-74466 USN-9020-1 |
| Ubuntu | 24.04:LTS | linux-azure-fde-7.0 | 7.0.0-1019.19~24.04.1 | UBUNTU-CVE-2026-74466 USN-9020-1 |
| Ubuntu | 24.04:LTS | linux-gcp-7.0 | 7.0.0-1017.19~24.04.1 | UBUNTU-CVE-2026-74466 USN-9020-1 |
| Ubuntu | 24.04:LTS | linux-hwe-7.0 | 7.0.0-42.42~24.04.1 | UBUNTU-CVE-2026-74466 USN-8959-1 |
| Ubuntu | 24.04:LTS | linux-oracle-7.0 | 7.0.0-1016.18~24.04.1 | UBUNTU-CVE-2026-74466 USN-9020-1 |
| Ubuntu | 24.04:LTS | linux-riscv-7.0 | 7.0.0-42.42.1~24.04.1 | UBUNTU-CVE-2026-74466 |
| Ubuntu | 26.04:LTS | linux | 7.0.0-42.42 | UBUNTU-CVE-2026-74466 USN-8959-1 |
| 15 more for Ubuntu in the JSON and on Ubuntu's page. | ||||
| SUSE | Linux Enterprise High Availability Extension 16.0 | kernel-default | 6.12.0-160000.41.1 | SUSE-SU-2026:24651-1 |
| SUSE | Linux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0 | kernel-64kb, kernel-docs, kernel-syms and 6 more | 6.12.0-160000.41.1 | SUSE-SU-2026:24662-1 |
| SUSE | Linux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0 | kernel-default-base | 6.12.0-160000.41.1.160000.2.32 | SUSE-SU-2026:24662-1 |
| SUSE | Linux Micro 6.2 | kernel-default-base | 6.12.0-160000.41.1.160000.2.32 | SUSE-SU-2026:24643-1 |
| SUSE | Linux Micro 6.2 | kernel-rt, kernel-64kb, kernel-source and 1 more | 6.12.0-160000.41.1 | SUSE-SU-2026:24643-1 |
| SUSE | Linux Micro Extras 6.2 | kernel-syms, kernel-obs-build | 6.12.0-160000.41.1 | SUSE-SU-2026:24648-1 |
| openSUSE | Leap 16.0 | kernel-default-base | 6.12.0-160000.41.1.160000.2.31 | openSUSE-SU-2026:22266-1 |
| openSUSE | Leap 16.0 | kernel-rt, dtb-aarch64, kernel-64kb and 9 more | 6.12.0-160000.41.1 | openSUSE-SU-2026:22266-1 |
| Alpaquita | 23 | linux-lts | 6.1.191-r0 | BELL-CVE-2026-74466 |
| Alpaquita | 25 | linux-lts | 6.12.115-r0 | BELL-CVE-2026-74466 |
| Alpaquita | stream | linux-lts | 6.18.58-r0 | BELL-CVE-2026-74466 |
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.
A MODERATE information disclosure flaw was found in the Linux kernel s390/zcrypt subsystem shipped in Red Hat Enterprise Linux 9 and 10 and Red Hat In-Vehicle OS 2. When a CPRB is about to be sent, the domain value extracted from a user-supplied CCA or EP11 ioctl structure is used as an array index after bounds checking but without a speculation barrier. Under special conditions, such as when a custom zcrypt device node is used under administrative load, a local attacker could exploit speculative execution to perform out-of-bounds reads and potentially disclose kernel memory contents. The issue is rated MODERATE because exploitation requires local access to the zcrypt device, an uncommon system configuration, and a successful speculative-execution side channel, limiting the practical impact to confidentiality. Red Hat Enterprise Linux 6, 7, and 8 are not affected because the vulnerable code is not present in those releases. For the affected Red Hat Enterprise Linux 9, Red Hat Enterprise Linux 10, and Red Hat In-Vehicle OS 2 releases, the fix has been deferred to a future update; the residual risk is considered low because triggering the flaw requires a custom device node setup with administrative load and only transient speculative reads are possible. Upstream addressed the issue by adding the missing array_index_nospec() call to prevent speculative execution where the domain value is used.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | kernel | Fix deferred | |
| Red Hat Enterprise Linux 6 | kernel | Not affected | |
| Red Hat Enterprise Linux 7 | kernel | Not affected | |
| Red Hat Enterprise Linux 7 | kernel-rt | Not affected | |
| Red Hat Enterprise Linux 8 | kernel | Not affected | |
| Red Hat Enterprise Linux 8 | kernel-rt | Not affected | |
| Red Hat Enterprise Linux 9 | kernel | Fix deferred | |
| Red Hat Enterprise Linux 9 | kernel-rt | Fix deferred |
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-74466.
References
- https://git.kernel.org/stable/c/55ac533c568a5dcaa41cd26d6e089f9dff2a7c22
- https://git.kernel.org/stable/c/59adeedebf02aa1c203de1d2b67ec45bfab7a3c6
- https://git.kernel.org/stable/c/82b62eda68abfb7a33ac40f24b8c4128c2891148
- https://git.kernel.org/stable/c/d11a260bd7dfc6f6ccd43e1b930050f24e70cd5f
- https://git.kernel.org/stable/c/dd1a334523ba533cba63caf593a7329d8e0e5e6e
- https://git.kernel.org/stable/c/e935cd525af4c6ed2e2c6404aa27ca19c7f39ddb