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 056D53A2E2E for ; Sun, 19 Jul 2026 15:03:38 +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=1784473419; cv=none; b=Ql/QSBBlGwBYviJYBynecTPyqgVBVnMxuIOHPaUEN6+mjKOc4uJlv8n4PFtGsSc9PL7t4tt7gzMKQlF6yoKGuTiHukCipvwbYcYqcMEchXd9ge+YmsN7pm/JMmw0WhkDMAfcH7Tf96CO0IsiawAmHVzfJTWLIgK7eXQzZ7xf0xo= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784473419; c=relaxed/simple; bh=omjqJwYwixWT7FKW9bloLiTd8e6rEHXbM0ZH+C3YCUg=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=Z95+Srinpc+2S51I2Y0LPLS1WCF+onIIb6+9uKChHogll1uzACLM1cL0/2x8guVkg20i8XV8zIJZY3nuDcjE1MTdBt/2+cj2Y1ls8wNZ7GnInhwdm2l9dga3sr/pccYXBRTHEFPkWOL9/ehHDTxQABIjnWa/eun4g6IKTWhOLMk= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=LCYE1rml; 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="LCYE1rml" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 68D5A1F000E9; Sun, 19 Jul 2026 15:03:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1784473417; bh=5kmSoowd3szCftLWLN++LB9U8Gpn9tZZSJdiYuDFZn8=; h=From:To:Cc:Subject:Date:Reply-To; b=LCYE1rml/rkiTqaaz/bIjRxFTpk3HzSHxTvymtJLjpTARXwLkfoi3urZCIsIOx6aD GwWRWS1mN8hR2fIRLyHpqXThuFUyRvsVUohX2L6kUTNwR/XkrSZzOd+4/EMRglMD1Q h5PIcnF2p0qcPR7vkauE1E8nsK56CUD179FTSuM4= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-64010: nfc: llcp: Fix use-after-free race in nfc_llcp_recv_cc() Date: Sun, 19 Jul 2026 16:57:50 +0200 Message-ID: <2026071909-CVE-2026-64010-4f09@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=4020; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=hu3liG7yuAGcYiQVeddWuzKr+IaRzAXypz744knzEWo=; b=owGbwMvMwCRo6H6F97bub03G02pJDFkxTzvd5R+ZWuxnL1XQqKq5GLsvx+uVe71ygRLDPMkjB a+0njl3xLIwCDIxyIopsnzZxnN0f8UhRS9D29Mwc1iZQIYwcHEKwESuv2CY7zRFWvpf4tX0NebC tYUTVDacZfrOyDDfwe+vLtu/Tfc0wqfU6kf2ep9NmBgKAA== 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: nfc: llcp: Fix use-after-free race in nfc_llcp_recv_cc() A race condition exists in the NFC LLCP connection state machine where the connection acceptance packet (CC) can be processed concurrently with socket release. This can lead to a use-after-free of the socket object. When nfc_llcp_recv_cc() moves the socket from the connecting_sockets list to the sockets list, it does so without holding the socket lock. If llcp_sock_release() is executing concurrently, it might have already unlinked the socket and dropped its references, which can result in nfc_llcp_recv_cc() linking a freed socket into the live list. Fix this by holding lock_sock() during the state transition and list movement in nfc_llcp_recv_cc(). After acquiring the lock, check if the socket is still hashed to ensure it hasn't already been unlinked and marked for destruction by the release path. This aligns the locking pattern with recv_hdlc() and recv_disc(). The Linux kernel CVE team has assigned CVE-2026-64010 to this issue. Affected and fixed versions =========================== Issue introduced in 3.6 with commit a69f32af86e389dd232b1bb2269e202c1bfcc60f and fixed in 5.10.259 with commit dce85215a6c7b0fd753f577a4c487f647119884c Issue introduced in 3.6 with commit a69f32af86e389dd232b1bb2269e202c1bfcc60f and fixed in 5.15.210 with commit bd08bb7443c501d2f2a71d529e4afcf11c9b07d2 Issue introduced in 3.6 with commit a69f32af86e389dd232b1bb2269e202c1bfcc60f and fixed in 6.1.176 with commit 0b45c31746e1523d5d482fda8fcf54a35ac417f1 Issue introduced in 3.6 with commit a69f32af86e389dd232b1bb2269e202c1bfcc60f and fixed in 6.6.143 with commit ee2d1a8a1833c5e56e9a1745e64b0b4edda732c2 Issue introduced in 3.6 with commit a69f32af86e389dd232b1bb2269e202c1bfcc60f and fixed in 6.12.93 with commit ad8a27d63cac96bac441edd002209ebd996e12fb Issue introduced in 3.6 with commit a69f32af86e389dd232b1bb2269e202c1bfcc60f and fixed in 6.18.35 with commit 650bdd8fdfab64a09ee474150313dbc48c374795 Issue introduced in 3.6 with commit a69f32af86e389dd232b1bb2269e202c1bfcc60f and fixed in 7.0.12 with commit b2a60f7f846faaf5c2cdad4ea6d3a33e5f863183 Issue introduced in 3.6 with commit a69f32af86e389dd232b1bb2269e202c1bfcc60f and fixed in 7.1 with commit b493ea2765cc17cb8aa7e7544a4b6dcb05b6ed77 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-64010 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/nfc/llcp_core.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/dce85215a6c7b0fd753f577a4c487f647119884c https://git.kernel.org/stable/c/bd08bb7443c501d2f2a71d529e4afcf11c9b07d2 https://git.kernel.org/stable/c/0b45c31746e1523d5d482fda8fcf54a35ac417f1 https://git.kernel.org/stable/c/ee2d1a8a1833c5e56e9a1745e64b0b4edda732c2 https://git.kernel.org/stable/c/ad8a27d63cac96bac441edd002209ebd996e12fb https://git.kernel.org/stable/c/650bdd8fdfab64a09ee474150313dbc48c374795 https://git.kernel.org/stable/c/b2a60f7f846faaf5c2cdad4ea6d3a33e5f863183 https://git.kernel.org/stable/c/b493ea2765cc17cb8aa7e7544a4b6dcb05b6ed77