{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-74611","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","state":"PUBLISHED","assignerShortName":"Linux","dateReserved":"2026-08-15T05:44:03.920Z","datePublished":"2026-08-22T15:31:57.534Z","dateUpdated":"2026-08-25T05:40:37.263Z"},"containers":{"cna":{"providerMetadata":{"orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux","dateUpdated":"2026-08-25T05:40:37.263Z"},"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\ntls: rx: restore msg_iter before TLS 1.3 optimistic retry\n\ntls_decrypt_sg() advances msg->msg_iter when it maps user pages for\nthe optimistic TLS 1.3 zero-copy path. If the decrypted record turns\nout not to be unpadded application data, tls_decrypt_sw() retries into\na kernel skb, but leaves the iterator advanced.\n\nThe subsequent copy from the skb then writes decrypted bytes again at\na later point in the caller iovecs while recvmsg() reports only the\npost-retry length. A TLS peer can trigger this after the receiver\nenables TLS_RX_EXPECT_NO_PAD.\n\nRevert the iterator by the number of bytes consumed by the optimistic\nmapping before retrying without zero-copy.\n\nAdd a selftest which sends a TLS 1.3 control record with\nTLS_RX_EXPECT_NO_PAD enabled and verifies that recvmsg() does not\noverwrite later iovecs beyond the returned length."}],"metrics":[{"cvssV3_1":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","baseScore":9.8,"baseSeverity":"CRITICAL"},"scenarios":[{"lang":"en","value":"AV:N - The bug is in kTLS software RX (tls_decrypt_sw/tls_sw_recvmsg) and is driven by TLS 1.3 records received from a remote TCP peer; per kernel CNA guidance, kTLS flaws triggered by peer ciphertext on an established connection are Network-reachable (e.g., malicious client to nginx/HAProxy/NVMe-oF-TLS server).\nAC:L - Once the receiver has TLS 1.3 kTLS RX with TLS_RX_EXPECT_NO_PAD, a remote peer can deterministically trigger the optimistic-decrypt retry by sending a non-application-data inner record (handshake/alert/KeyUpdate) or padded data; no race, special heap layout, or rare kernel build is required.\nPR:N - Exploitation requires only being the remote TLS peer on an established kTLS connection; the attacker needs no credentials or Linux capabilities on the victim host. TLS_RX_EXPECT_NO_PAD is a receiver-side performance option set by the service, not an attacker privilege gate.\nUI:N - No victim user action beyond normal automated server operation (maintaining a TLS session and calling recvmsg on kTLS sockets). The attacker triggers the flaw solely by sending protocol-valid TLS records over the network.\nS:U - The out-of-bounds write corrupts user-space iovec buffers of the process owning the kTLS socket within the same security authority; it does not cross a VM, IOMMU, or sandbox boundary to another security domain.\nC:H - skb_copy_datagram_msg writes decrypted peer-controlled bytes past the recvmsg-reported length into adjacent user buffers. This memory corruption can be leveraged for information disclosure via heap/stack grooming even though the immediate primitive is a write.\nI:H - The remote peer controls the decrypted payload written out-of-bounds (up to a full TLS record, roughly 16 KiB) into later iovecs while recvmsg under-reports bytes copied, giving a reliable user-space memory corruption primitive suitable for control-flow or data hijack in privileged daemons.\nA:H - Corrupting adjacent application buffers in kTLS-enabled daemons (web proxies, storage targets, RPC endpoints) can crash workers or destabilize the service; the silent mismatch between returned length and bytes written also enables persistent denial of service on long-lived connections."}]}],"affected":[{"product":"Linux","vendor":"Linux","defaultStatus":"unaffected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["net/tls/tls_sw.c","tools/testing/selftests/net/tls.c"],"versions":[{"version":"ce61327ce989b63c0bd1cc7afee00e218ee696ac","lessThan":"68787940274ec89f41dc91b1a68ee1a16a90735f","status":"affected","versionType":"git"},{"version":"ce61327ce989b63c0bd1cc7afee00e218ee696ac","lessThan":"3c837266a734e2a22b24d2d567404a501d405835","status":"affected","versionType":"git"},{"version":"ce61327ce989b63c0bd1cc7afee00e218ee696ac","lessThan":"1c8629651cb54f7b51db8fc0b1a9944e4a4b0f5e","status":"affected","versionType":"git"}]},{"product":"Linux","vendor":"Linux","defaultStatus":"affected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["net/tls/tls_sw.c","tools/testing/selftests/net/tls.c"],"versions":[{"version":"6.0","status":"affected"},{"version":"0","lessThan":"6.0","status":"unaffected","versionType":"semver"},{"version":"6.18.45","lessThanOrEqual":"6.18.*","status":"unaffected","versionType":"semver"},{"version":"7.1.9","lessThanOrEqual":"7.1.*","status":"unaffected","versionType":"semver"},{"version":"7.2","lessThanOrEqual":"*","status":"unaffected","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.0","versionEndExcluding":"6.18.45"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.0","versionEndExcluding":"7.1.9"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.0","versionEndExcluding":"7.2"}]}]}],"references":[{"url":"https://git.kernel.org/stable/c/68787940274ec89f41dc91b1a68ee1a16a90735f"},{"url":"https://git.kernel.org/stable/c/3c837266a734e2a22b24d2d567404a501d405835"},{"url":"https://git.kernel.org/stable/c/1c8629651cb54f7b51db8fc0b1a9944e4a4b0f5e"}],"title":"tls: rx: restore msg_iter before TLS 1.3 optimistic retry","x_generator":{"engine":"bippy-1.2.0"}}}}