{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-74611 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-74611 is a critical vulnerability in Linux, published on 22 Aug 2026."},"fix_prompt":"Check this codebase for CVE-2026-74611 and fix it if it is affected.\n\nWhat it is: CVE-2026-74611 is a critical vulnerability in Linux, published on 22 Aug 2026. \nExploitation: There is no known exploitation of CVE-2026-74611 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-74611/ (Markdown: https://insights.sbomify.com/CVE-2026-74611/index.md)","id":"CVE-2026-74611","markdown":"https://insights.sbomify.com/CVE-2026-74611/index.md","name":"CVE-2026-74611","record":{"aliases":["AZL-97334","BELL-CVE-2026-74611","DEBIAN-CVE-2026-74611","GHSA-g4xp-j3j4-vmrq","UBUNTU-CVE-2026-74611"],"analysis":null,"analysis_generated_by":null,"assigner":"Linux","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"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-\u003emsg_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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"tls: rx: restore msg_iter before TLS 1.3 optimistic retry","id":"CVE-2026-74611","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"veth: fix skb length accounting after XDP frag adjustment","id":"CVE-2026-74612"},"packages":[],"prev":{"headline":"tls: don't leave a full plaintext sk_msg ring unpushed","id":"CVE-2026-74610"},"products":["Linux"],"published":"2026-08-22","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-21","vendors":["Linux"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-74611/"}