{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80904 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-80904 is a vulnerability in Linux, published on 4 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-80904 and fix it if it is affected.\n\nWhat it is: CVE-2026-80904 is a vulnerability in Linux, published on 4 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-80904 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-80904/ (Markdown: https://insights.sbomify.com/CVE-2026-80904/index.md)","id":"CVE-2026-80904","markdown":"https://insights.sbomify.com/CVE-2026-80904/index.md","name":"CVE-2026-80904","record":{"aliases":["AZL-99525","BELL-CVE-2026-80904","DEBIAN-CVE-2026-80904","GHSA-vp2x-h945-mvcw","UBUNTU-CVE-2026-80904"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel TLS","requires_auth":"none","summary":"An attacker can bypass TLS authentication checks by exploiting a missing error check in the Linux kernel's TLS splice read function, allowing delivery of unauthenticated data.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnet/tls: Fail tls_sw_splice_read() after a failed async decrypt\n\nWhen an async decrypt fails, tls_decrypt_done() records the error in\nctx-\u003easync_wait.err and calls tls_err_abort(), which stores it in\nsk_err. tls_sw_recvmsg() and tls_sw_read_sock() each read\nasync_wait.err once they hold the reader lock and fail the call: a\nrecord that did not authenticate breaks the connection.\n\ntls_sw_splice_read() has no such check, and sk_err does not stand in\nfor one. tls_rx_rec_wait() tests sk_err only inside the loop it\nskips whenever a record is already parsed, and the first reader to\nreach sock_error() clears it, while async_wait.err persists. A\nsplice therefore keeps delivering records on a connection that\nrecvmsg() and read_sock() refuse to read.\n\nRead async_wait.err in tls_sw_splice_read() as the other two readers\ndo.","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":"net/tls: Fail tls_sw_splice_read() after a failed async decrypt","id":"CVE-2026-80904","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"net: tap: fix wrong transport_header when sending VLAN-tagged frame","id":"CVE-2026-80905"},"packages":[],"prev":{"headline":"drm/xe/oa: Fix sync entry leak on OA config emit failure","id":"CVE-2026-80903"},"products":["Linux"],"published":"2026-09-04","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-09-04","vendors":["Linux"]},"summary":"An attacker can bypass TLS authentication checks by exploiting a missing error check in the Linux kernel's TLS splice read function, allowing delivery of unauthenticated data.","url":"https://insights.sbomify.com/CVE-2026-80904/"}