{"api_version":"1","generated_at":"2026-09-11T09:57:20+00:00","cve":"CVE-2026-80850","urls":{"html":"https://cve.report/CVE-2026-80850","api":"https://cve.report/api/cve/CVE-2026-80850.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-80850","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-80850"},"summary":{"title":"tcp: fix AO info use-after-free in tcp_ao_connect_init()","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->ao_info and frees it directly.\n\nThe receive path can find the socket in the ehash and load tp->ao_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.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-04 16:18:13","updated_at":"2026-09-04 16:18:13"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/594ba77210a1f065832211851a2d7e14d11fcbdb","name":"https://git.kernel.org/stable/c/594ba77210a1f065832211851a2d7e14d11fcbdb","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/d17e88b6b60ff4ef64e0dd1444f935cb13dee1cd","name":"https://git.kernel.org/stable/c/d17e88b6b60ff4ef64e0dd1444f935cb13dee1cd","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/284d7fd0eec8774bd6214921fbf525cf907c590e","name":"https://git.kernel.org/stable/c/284d7fd0eec8774bd6214921fbf525cf907c590e","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/70051a57786d5b23f059fbaf5c8241eca14d42ed","name":"https://git.kernel.org/stable/c/70051a57786d5b23f059fbaf5c8241eca14d42ed","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/ea30dc5267e367b8a5e1e06cc074f813bcbf18b2","name":"https://git.kernel.org/stable/c/ea30dc5267e367b8a5e1e06cc074f813bcbf18b2","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-80850","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80850","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 248411b8cb8974a1e1c8e43123c1e682fbd64969 594ba77210a1f065832211851a2d7e14d11fcbdb git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 248411b8cb8974a1e1c8e43123c1e682fbd64969 70051a57786d5b23f059fbaf5c8241eca14d42ed git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 248411b8cb8974a1e1c8e43123c1e682fbd64969 284d7fd0eec8774bd6214921fbf525cf907c590e git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 248411b8cb8974a1e1c8e43123c1e682fbd64969 d17e88b6b60ff4ef64e0dd1444f935cb13dee1cd git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 248411b8cb8974a1e1c8e43123c1e682fbd64969 ea30dc5267e367b8a5e1e06cc074f813bcbf18b2 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.7","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.7 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.108 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.49 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1.13 7.1.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.3 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3-rc1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"80850","cve":"CVE-2026-80850","epss":"0.001710000","percentile":"0.067040000","score_date":"2026-09-07","updated_at":"2026-09-08 00:05:27"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["net/ipv4/tcp_ao.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"594ba77210a1f065832211851a2d7e14d11fcbdb","status":"affected","version":"248411b8cb8974a1e1c8e43123c1e682fbd64969","versionType":"git"},{"lessThan":"70051a57786d5b23f059fbaf5c8241eca14d42ed","status":"affected","version":"248411b8cb8974a1e1c8e43123c1e682fbd64969","versionType":"git"},{"lessThan":"284d7fd0eec8774bd6214921fbf525cf907c590e","status":"affected","version":"248411b8cb8974a1e1c8e43123c1e682fbd64969","versionType":"git"},{"lessThan":"d17e88b6b60ff4ef64e0dd1444f935cb13dee1cd","status":"affected","version":"248411b8cb8974a1e1c8e43123c1e682fbd64969","versionType":"git"},{"lessThan":"ea30dc5267e367b8a5e1e06cc074f813bcbf18b2","status":"affected","version":"248411b8cb8974a1e1c8e43123c1e682fbd64969","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["net/ipv4/tcp_ao.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.7"},{"lessThan":"6.7","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.108","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.49","versionType":"semver"},{"lessThanOrEqual":"7.1.*","status":"unaffected","version":"7.1.13","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.3","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.108","versionStartIncluding":"6.7","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.49","versionStartIncluding":"6.7","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1.13","versionStartIncluding":"6.7","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.3","versionStartIncluding":"6.7","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc1","versionStartIncluding":"6.7","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"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->ao_info and frees it directly.\n\nThe receive path can find the socket in the ehash and load tp->ao_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."}],"providerMetadata":{"dateUpdated":"2026-09-04T15:55:00.588Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/594ba77210a1f065832211851a2d7e14d11fcbdb"},{"url":"https://git.kernel.org/stable/c/70051a57786d5b23f059fbaf5c8241eca14d42ed"},{"url":"https://git.kernel.org/stable/c/284d7fd0eec8774bd6214921fbf525cf907c590e"},{"url":"https://git.kernel.org/stable/c/d17e88b6b60ff4ef64e0dd1444f935cb13dee1cd"},{"url":"https://git.kernel.org/stable/c/ea30dc5267e367b8a5e1e06cc074f813bcbf18b2"}],"title":"tcp: fix AO info use-after-free in tcp_ao_connect_init()","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-80850","datePublished":"2026-09-04T15:55:00.588Z","dateReserved":"2026-08-26T14:34:25.797Z","dateUpdated":"2026-09-04T15:55:00.588Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-04 16:18:13","lastModifiedDate":"2026-09-04 16:18:13","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"80850","Ordinal":"1","Title":"tcp: fix AO info use-after-free in tcp_ao_connect_init()","CVE":"CVE-2026-80850","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"80850","Ordinal":"1","NoteData":"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->ao_info and frees it directly.\n\nThe receive path can find the socket in the ehash and load tp->ao_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.","Type":"Description","Title":"tcp: fix AO info use-after-free in tcp_ao_connect_init()"}]}}}