CVSS 3.1
9.8 criticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HCritical (9.8) in linux linux. EPSS 0.5% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExplain CVE-2026-74611 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-74611?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-74611?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-74611 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.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Linux | 6.0 and later |
| 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.45 |
| Linux | 7.1 | 7.1.9 |
| Linux | later releases | 7.2 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12 | linux | 6.1.192-1 | DEBIAN-CVE-2026-74611 |
| Debian | 12 | linux-6.12 | 6.12.115-2~deb12u1 | DEBIAN-CVE-2026-74611 |
| Debian | 13 | linux | 6.12.115-2 | DEBIAN-CVE-2026-74611 |
| Debian | 14 | linux | 7.1.9-1 | DEBIAN-CVE-2026-74611 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2026-74611 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2026-74611 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2026-74611 |
| Ubuntu | 22.04:LTS | linux-riscv, linux-aws-6.2, linux-aws-6.5 and 40 more | no fix listed | UBUNTU-CVE-2026-74611 |
| Ubuntu | 24.04:LTS | linux, linux-aws, linux-gcp and 43 more | no fix listed | UBUNTU-CVE-2026-74611 |
| Ubuntu | 24.04:LTS | linux-aws-7.0 | 7.0.0-1017.18~24.04.1 | UBUNTU-CVE-2026-74611 USN-9020-1 |
| Ubuntu | 24.04:LTS | linux-azure-fde-7.0 | 7.0.0-1019.19~24.04.1 | UBUNTU-CVE-2026-74611 USN-9020-1 |
| Ubuntu | 24.04:LTS | linux-gcp-7.0 | 7.0.0-1017.19~24.04.1 | UBUNTU-CVE-2026-74611 USN-9020-1 |
| Ubuntu | 24.04:LTS | linux-hwe-7.0 | 7.0.0-42.42~24.04.1 | UBUNTU-CVE-2026-74611 USN-8959-1 |
| Ubuntu | 24.04:LTS | linux-nvidia-tegra | 6.8.0-1036.39 | UBUNTU-CVE-2026-74611 USN-8886-1 |
| Ubuntu | 24.04:LTS | linux-oracle-7.0 | 7.0.0-1016.18~24.04.1 | UBUNTU-CVE-2026-74611 USN-9020-1 |
| Ubuntu | 24.04:LTS | linux-riscv-7.0 | 7.0.0-42.42.1~24.04.1 | UBUNTU-CVE-2026-74611 |
| 16 more for Ubuntu in the JSON and on Ubuntu's page. | ||||
| SUSE | Linux Enterprise High Availability Extension 15 SP6, Linux Enterprise Live Patching 15 SP6 | kernel-default | 6.4.0-150600.23.143.1 | SUSE-SU-2026:4934-1 |
| SUSE | Linux Enterprise High Availability Extension 15 SP7, Linux Enterprise Live Patching 15 SP7, Linux Enterprise Module for Legacy 15 SP7 and 1 more | kernel-default | 6.4.0-150700.53.87.3 | SUSE-SU-2026:4935-1 |
| SUSE | Linux Enterprise High Availability Extension 16.0 | kernel-default | 6.12.0-160000.40.1 | SUSE-SU-2026:24437-1 |
| SUSE | Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_33 | 1-150600.13.5.1 | SUSE-SU-2026:4934-1 |
| SUSE | Linux Enterprise Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7-RT_Update_22 | 1-150700.1.3.1 | SUSE-SU-2026:4940-1 |
| SUSE | Linux Enterprise Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7_Update_23 | 1-150700.15.3.2 | SUSE-SU-2026:4935-1 |
| SUSE | Linux Enterprise Module for Basesystem 15 SP7 | kernel-64kb, kernel-source, kernel-default and 1 more | 6.4.0-150700.53.87.3 | SUSE-SU-2026:4935-1 |
| SUSE | Linux Enterprise Module for Basesystem 15 SP7 | kernel-default-base | 6.4.0-150700.53.87.3.150700.17.49.2 | SUSE-SU-2026:4935-1 |
| SUSE | Linux Enterprise Module for Development Tools 15 SP7 | kernel-docs, kernel-source | 6.4.0-150700.53.87.3 | SUSE-SU-2026:4935-1 |
| SUSE | Linux Enterprise Module for Development Tools 15 SP7 | kernel-obs-build | 6.4.0-150700.53.87.2 | SUSE-SU-2026:4935-1 |
| SUSE | Linux Enterprise Module for Development Tools 15 SP7 | kernel-syms | 6.4.0-150700.53.87.1 | SUSE-SU-2026:4935-1 |
| SUSE | Linux Enterprise Module for Public Cloud 15 SP7 | kernel-azure | 6.4.0-150700.53.87.3 | SUSE-SU-2026:4935-1 |
| 16 more for SUSE in the JSON and on SUSE's page. | ||||
| openSUSE | Leap 16.0 | kernel-default-base | 6.12.0-160000.40.1.160000.2.29 | openSUSE-SU-2026:22167-1 |
| openSUSE | Leap 16.0 | kernel-rt, dtb-aarch64, kernel-64kb and 9 more | 6.12.0-160000.40.1 | openSUSE-SU-2026:22167-1 |
| openSUSE | Leap 16.1 | kernel-default-base | 6.12.0-160100.9.1.160100.3.14 | openSUSE-SU-2026:22309-1 |
| openSUSE | Leap 16.1 | kernel-nvidia64kb, kernel-syms-nvidia, kernel-source-nvidia | 6.12.0-160100.6.1 | openSUSE-SU-2026:22313-1 |
| openSUSE | Leap 16.1 | kernel-rt, dtb-aarch64, kernel-64kb and 9 more | 6.12.0-160100.9.1 | openSUSE-SU-2026:22309-1 |
| Azure Linux | 3 | kernel | 6.6.161.1-1 | AZL-97334 |
| Alpaquita | 23 | linux-lts | 6.1.191-r0 | BELL-CVE-2026-74611 |
| Alpaquita | 25 | linux-lts | 6.12.115-r0 | BELL-CVE-2026-74611 |
| Alpaquita | stream | linux-lts | 6.18.46-r0 | BELL-CVE-2026-74611 |
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; Microsoft's Azure Linux vulnerability data, MIT; 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 rates this Moderate.
A user-buffer overwrite can occur in the Linux kernel TLS 1.3 receive path due to incorrect handling of the message iterator during an optimistic zero-copy retry. `tls_decrypt_sg()` advances `msg->msg_iter` while mapping the caller-provided iovecs for the optimistic zero-copy receive path. If the decrypted TLS 1.3 record is subsequently determined not to be unpadded application data, `tls_decrypt_sw()` falls back to decrypting through a kernel skb. Before the fix, this retry occurred without restoring the iterator to its original position.
As a result, the subsequent copy from the skb starts at the already advanced iterator position and can write decrypted peer-controlled data into later portions of the caller-provided iovecs. `recvmsg()` nevertheless reports only the length associated with the retried receive operation. The receiving application can therefore observe memory beyond the range implied by the `recvmsg()` return value being unexpectedly modified.
The vulnerable path is remotely triggerable by a TLS peer when the receiving application uses kernel TLS (kTLS) with TLS 1.3 RX and enables `TLS_RX_EXPECT_NO_PAD`. A peer can then send a TLS record, such as a control record, that causes the optimistic zero-copy path to fall back to the retry path.
The directly demonstrated impact is corruption of the receiving process's user buffers. This is not an arbitrary kernel-memory write: the erroneous copy remains within user iovec memory previously supplied by the receiving application to `recvmsg()`. No kernel memory corruption, kernel privilege escalation, or arbitrary code execution has been demonstrated. Depending on how the affected application allocates and subsequently interprets its receive buffers, the unexpected overwrite can corrupt application state or cause application-level denial of service.
Integrity impact is therefore directly supported, while availability impact is application-dependent. Confidentiality impact is less direct because the primitive itself writes peer-controlled decrypted data rather than exposing kernel or process memory to the attacker. A paranoid assessment may retain limited confidentiality and integrity impact.
The practical assessment therefore accounts for the remotely reachable attack surface while recognizing the specific kTLS configuration prerequisite and the fact that the demonstrated overwrite is confined to caller-provided user buffers rather than kernel memory.
To mitigate this issue, prevent module tls from being loaded. Please see https://access.redhat.com/solutions/41278 for how to blacklist a kernel module to prevent it from loading automatically.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | kernel | Affected | |
| 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 | Affected | |
| Red Hat Enterprise Linux 9 | kernel-rt | Affected |
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-74611.