{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80850 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-80850 is an use after free vulnerability in Linux, published on 4 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-80850 and fix it if it is affected.\n\nWhat it is: CVE-2026-80850 is an use after free vulnerability in Linux, published on 4 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-80850 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-80850/ (Markdown: https://insights.sbomify.com/CVE-2026-80850/index.md)","id":"CVE-2026-80850","markdown":"https://insights.sbomify.com/CVE-2026-80850/index.md","name":"CVE-2026-80850","record":{"aliases":["BELL-CVE-2026-80850","DEBIAN-CVE-2026-80850","GHSA-cpgq-xw99-wp3q","UBUNTU-CVE-2026-80850"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A race condition in Linux kernel TCP-AO handling allows local attackers to trigger a use-after-free, potentially leading to code execution or privilege escalation.","user_interaction":"not_required","vuln_class":"use_after_free"},"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\ntcp: fix AO info use-after-free in tcp_ao_connect_init()\n\ntcp_v4_connect() adds a SYN-SENT socket to the ehash before calling\ntcp_connect().  If TCP-AO is configured, tcp_connect() first verifies that\na key matches the peer and the bound device's current L3 master.\ntcp_ao_connect_init() later resolves the L3 master again and removes keys\nwhich do not match it.\n\nThe socket lock does not stabilize the bound device's VRF membership.\nDetaching the device from its VRF between the initial validation and the\nL3-master calculation in tcp_ao_connect_init() can therefore make the\nvalidation succeed while initialization observes the default L3 domain and\nremoves the only key.  The subsequent AO lookup then fails, so the no-key\npath clears tp-\u003eao_info and frees it directly.\n\nThe receive path can find the socket in the ehash and load tp-\u003eao_info\nunder RCU before acquiring the socket lock.  A reader which loaded the old\npointer can thus continue into tcp_inbound_ao_hash() after the direct free.\n\nThe issue was found during a static audit of TCP-AO object lifetime.  An\nunprivileged reproducer in self-created user and network namespaces raced\nconnect() with detaching a veth from its VRF while sending TCP-AO segments.\nIt triggered the same KASAN report on two fresh boots:\n\n  BUG: KASAN: slab-use-after-free in tcp_inbound_ao_hash+0x585/0x19f0\n  Write of size 8 at addr ffff88800bf88128 by task tcp_ao_vrf_race/232\n\n  Call Trace:\n   tcp_inbound_ao_hash+0x585/0x19f0\n   tcp_inbound_hash+0x677/0xa80\n   tcp_v4_rcv+0x1c3e/0x3ab0\n\n  Allocated by task 235:\n   tcp_ao_alloc_info+0x43/0xf0\n   tcp_ao_add_cmd+0xdf7/0x13b0\n   do_tcp_setsockopt+0x168c/0x2640\n\n  Freed by task 235:\n   kfree+0x1b8/0x550\n   tcp_connect+0x252/0x4f00\n   tcp_v4_connect+0x1114/0x1720\n\nThe bad address is 40 bytes inside the freed 128-byte object, matching the\ntcp_ao_info counters.key_not_found field.  The two runs used 1000 attempts\neach, reached the no-key path 366 and 411 times, and produced one and two\nKASAN reports respectively.  With this change, the same reproducer reached\nthe no-key path 366 times in 1000 attempts without a KASAN report or oops.\n\nUse tcp_ao_destroy_sock() for the no-key path.  It unpublishes the AO info,\nupdates the socket memory and static-key accounting, and defers the free\nuntil after an RCU grace period.\n\nAlso drop the WARN_ON_ONCE() and its stale comment.  The VRF detach race\nmakes the no-key state reachable during normal operation, so it is a\nhandled condition rather than an impossible assertion.  On panic_on_warn\nkernels the WARN would turn this handled race into a kernel panic.","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":"tcp: fix AO info use-after-free in tcp_ao_connect_init()","id":"CVE-2026-80850","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"gtp: serialize PDP context updates","id":"CVE-2026-80851"},"packages":[],"prev":{"headline":"net/tcp-ao: fix use-after-free of current_key on reconnect to another peer","id":"CVE-2026-80849"},"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-10-19","vendors":["Linux"]},"summary":"A race condition in Linux kernel TCP-AO handling allows local attackers to trigger a use-after-free, potentially leading to code execution or privilege escalation.","url":"https://insights.sbomify.com/CVE-2026-80850/"}