From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 1559E38D415 for ; Sun, 19 Jul 2026 12:02:21 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784462543; cv=none; b=Cb7C/Bs2CKHFmjoHVOFRoKOqFG+0KAyb6Qvgo4yFUMPX1yfoe8/jp8eQi11G1I0QMO8p1yY2LSTF9op+G7DVweZrRmEHzJyNXxqC8xTy1m4akXNxLBtexzKB7VY7RHgUmiy0DE3SqWKfexSZ+Di09z85jwv2vXkRQF3wYeyOAV8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784462543; c=relaxed/simple; bh=seDH7hPAx8tigAJSiEMC9TGltsPkwTNQE5iCUgv8xwY=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=atHIFkhMtv8Oz0sfyY3Qo6TwOVND5SIos+qObbHZM0qFbcBdDquChlM/VUuSGtRpr6HIlsHi946JS8f3OnW1Pw+ZWboqn+4CADgd+yQoo06yESlCwNy7Z4d0TJ8yK6IVV+x/W04KzmWEjMCORX4eHRwptQMJeLJsBFk/f7lH58s= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=ljEINZZF; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="ljEINZZF" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 2CC4B1F000E9; Sun, 19 Jul 2026 12:02:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1784462541; bh=UF6FqqC00EPmbsVyPbiizIiFatuCbBvva+fo/c7o2QI=; h=From:To:Cc:Subject:Date:Reply-To; b=ljEINZZFQVb7kj/JtNbTwJCaPgbbQ1wWryCgaDPuJ8D1knIPxCHY0j3dR/UniWr0K OZAsKwsQfdsoXUX+zu2L0R+RKHWaPVnCuv+kIotto+4YCVA1AwRoq3dlYKoCMBvxqh YcsyR1LGqHxfMkyvkuyfferNuHkxWPzo/wEgE3ss= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-53389: net/tcp-ao: fix use-after-free of key in del_async path Date: Sun, 19 Jul 2026 14:01:55 +0200 Message-ID: <2026071955-CVE-2026-53389-36cb@gregkh> X-Mailer: git-send-email 2.55.0 Reply-To: , Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=2957; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=UBudiSH3o8Unz0OtHy9n5mdNSCQEMWKz+8fFW4jMtSg=; b=owGbwMvMwCRo6H6F97bub03G02pJDFkxezbfdz4ssnGTzrdTncFcX+24+81bNRZ6F2w4I3Vlg cftzsTyjlgWBkEmBlkxRZYv23iO7q84pOhlaHsaZg4rE8gQBi5OAZhIJS/Dgh2fymUEev8LTznt 3x29SeFyx+TH+xnm2Ure3jKhX1Zkqapu5B87yQnpk6aIAQA= X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman Description =========== In the Linux kernel, the following vulnerability has been resolved: net/tcp-ao: fix use-after-free of key in del_async path In tcp_ao_delete_key(), the del_async path skips the current_key and rnext_key validity checks present in the synchronous path, assuming these pointers are always NULL on LISTEN sockets. However, if a key was added with set_current=1/set_rnext=1 while the socket was in CLOSE state, current_key and rnext_key will be non-NULL after listen() transitions the socket to LISTEN. When such a key is deleted with del_async=1, hlist_del_rcu() and call_rcu() free the key without clearing the dangling pointers. After the RCU grace period, getsockopt(TCP_AO_INFO) dereferences current_key->sndid and rnext_key->rcvid from freed slab memory. Clear current_key and rnext_key in the del_async path when they reference the key being deleted. The Linux kernel CVE team has assigned CVE-2026-53389 to this issue. Affected and fixed versions =========================== Issue introduced in 6.7 with commit d6732b95b6fbbc6d5bb9d2f809e275763640c4a2 and fixed in 6.12.95 with commit 6ce7ef41743740ce15c2061561b784148b565b3f Issue introduced in 6.7 with commit d6732b95b6fbbc6d5bb9d2f809e275763640c4a2 and fixed in 6.18.38 with commit e77fbefd1269b5c123e7c651a1ebdce1b87d19a0 Issue introduced in 6.7 with commit d6732b95b6fbbc6d5bb9d2f809e275763640c4a2 and fixed in 7.1.3 with commit 7ddc29a094d96e9b3aa280433c6dc443df9eabf2 Issue introduced in 6.7 with commit d6732b95b6fbbc6d5bb9d2f809e275763640c4a2 and fixed in 7.2-rc1 with commit 5ba9950bc9078e19b69cca1e56d1553b125c6857 Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2026-53389 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: net/ipv4/tcp_ao.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: https://git.kernel.org/stable/c/6ce7ef41743740ce15c2061561b784148b565b3f https://git.kernel.org/stable/c/e77fbefd1269b5c123e7c651a1ebdce1b87d19a0 https://git.kernel.org/stable/c/7ddc29a094d96e9b3aa280433c6dc443df9eabf2 https://git.kernel.org/stable/c/5ba9950bc9078e19b69cca1e56d1553b125c6857