Linux Kernel: TCP-AO use-after-free in tcp_ao_destroy_sock (CVE-2026-64459)
A use-after-free vulnerability in the Linux kernel TCP-AO implementation allows an unprivileged attacker to trigger kernel-level memory corruption and potential crashes via a race condition during socket connection.
CVE search metadata
CVE search record: CVE-2026-64459. Severity: critical. CVSS: 9.8. EPSS: 0.65%. KEV: no. Product: Linux kernel. Brief: Linux Kernel: TCP-AO use-after-free in tcp_ao_destroy_sock (CVE-2026-64459). Brief link: https://feed.craftedsignal.io/briefs/2026-11-linux-kernel-tcp-ao-uaf-cve-2026-64459/
Triage facts
Revision 1- Applicability
- Linux kernel
- Evidence
- Unknown
- Severity
- Critical
- Action
- Elevated
- Sources
- 2 public sources
- Freshness
- Revision 1Nov 18, 22:54 UTC
- Vulnerabilities
- 1 CVE
- Source quality
- A1
Overview
A use-after-free vulnerability exists in the Linux kernel's TCP-AO (Authentication Option) implementation within tcp_ao_destroy_sock(). The vulnerability stems from the removal of an RCU grace period when freeing TCP-AO info or keys. This enables a race condition where a reader in softirq context may access memory that has already been freed, leading to potential kernel oops, memory disclosure, or control-flow hijacking. An unprivileged user can trigger this flaw by spraying forged TCP-AO segments against a connection attempt.
Attack Chain
- Attacker sets up a process within a network namespace to create a TCP socket with TCP_MD5SIG and TCP_AO_ADD_KEY.
- Attacker initiates a
connect()call, placing the socket intoTCP_SYN_SENTstate and inserting it into the inet ehash. - Attacker triggers
tcp_ao_destroy_sock()by forcing a race condition during the connection process. - Concurrently, the attacker uses raw sockets to spray forged TCP-AO segments toward the socket's four-tuple.
- The kernel's
tcp_v4_rcv()handler, running in softirq context on another CPU, retrieves the socket from the ehash. - The handler attempts to perform an AO lookup using the already-freed
tp->ao_infopointer. - The kernel accesses reclaimed or poison memory, resulting in a general protection fault or kernel panic.
Impact
Successful exploitation leads to a kernel crash (kernel oops) or potential arbitrary kernel memory reads and control-flow hijacking. This vulnerability affects unprivileged users who can manipulate local network namespaces to trigger the race condition.
Recommendation
Upgrade the Linux kernel to a patched version. Based on the advisory, versions 6.18.39, 7.1.4, and 7.2 (or later) contain the fix by restoring the RCU grace period via call_rcu() in tcp_ao_destroy_sock().
Threat Hunt
Identify abnormal kernel crash patterns or General Protection Faults (GPF) in dmesg/kernel logs specifically involving __tcp_ao_do_lookup, tcp_inbound_hash, and tcp_v4_rcv. Focus on systems showing 'wild-memory-access' KASAN reports or GPF associated with non-canonical addresses shortly after socket connection establishment (TCP_SYN_SENT).
Data: kernel_logs, dmesg
Mitigations
Upgrade affected Linux kernel installations to version 6.18.39, 7.1.4, or 7.2 or later.
Gaps
- No specific Sigma detection rule is possible for this race condition as it manifests as a kernel panic or memory access violation rather than a distinct observable pattern in user-space or common system logs.