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 B20873783A0 for ; Sat, 15 Aug 2026 06:27:50 +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=1786775271; cv=none; b=UCaj7doTD041uMYpw0+UPBEeNDIBGnDpnH4uTI1yQ3PT+PvGgUow/Z1iMp55Z4wbEGWrVaN3ouAZuBjNdzXH/lreOBv5Fr455ItjlW/hrrKNgSc9+Nx7BPLILdgATuZ3DylOsEaY1kY+zlepalOLYfg07eARLP0sy68np4edmEA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786775271; c=relaxed/simple; bh=q2Co+vgfkObEzwrdhVKHsTVzNecvFnQUxbTs+85viEY=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=iOMxzT77rZV3hNWEjRN8byBo8x4Deo5O6kfDRqnd4vwgNPIjEXBOpTviWdzo9DTSUhICiraVq5ng2dNgL09a1pdoVp3nVN/G49tD9Kw0cqy3hVRtjVKGd1UR5VnqpeS77ijJ5nYThdplzPWxId/zBqCULlj3H0OSiyGtLqk3m6E= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=rKOhSv2g; 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="rKOhSv2g" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 10EFB1F000E9; Sat, 15 Aug 2026 06:27:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1786775270; bh=tzz5E+cV37TAZR0nzj+3WFWTGYokQj17VPajB0O+G+w=; h=From:To:Cc:Subject:Date:Reply-To; b=rKOhSv2gHhzFwKC0tLkR4UrtmHbefNSPNVWQlGzAyCCk3NOui1VQwHcwtYF8n1Q3A A85Hs0npPJVVxF4fZDdk4WY28XPSubLcPJhkRemSTGF8HAEOsOih9aGRTRO2GVdXpJ iw9bQ1qReXGHSTFOtzBgUlU+ZnZFdtKs0zsyr5fY= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-72430: net/sched: act_ct: fix nf_connlabels leak on two error paths Date: Sat, 15 Aug 2026 15:08:29 +0900 Message-ID: <2026081527-CVE-2026-72430-3360@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=3235; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=XwumcRuNoiTER9W7eO8emhnz/4yEEg/a8kRkTtexO4k=; b=owGbwMvMwCRo6H6F97bub03G02pJDFkNDJ//m38QaTe4fTzBdwmj8ozUspm/otgZFldURXnHx N8/ULW6I5aFQZCJQVZMkeXLNp6j+ysOKXoZ2p6GmcPKBDKEgYtTACZy045hwZG7Tax/GurzS50/ +H42Mo5SPnj/KsOCTe+KzxyWdz/Q6/lqff3ZmT+2rHV0BQA= 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/sched: act_ct: fix nf_connlabels leak on two error paths tcf_ct_fill_params() calls nf_connlabels_get() (setting put_labels) when TCA_CT_LABELS is present, but two later error sites use a bare return instead of "goto err", skipping the err: nf_connlabels_put() cleanup. They also precede the "p->put_labels = put_labels" assignment, so the tcf_ct_params_free() fallback does not release the count either. Each failed RTM_NEWACTION on these paths leaks one nf_connlabels reference: net->ct.labels_used is incremented and never released. The action is reachable with CAP_NET_ADMIN over the netns, i.e. from an unprivileged user namespace on default-userns kernels. Impact: an unprivileged user with CAP_NET_ADMIN over a network namespace (e.g. via user namespaces) leaks one nf_connlabels reference per failed RTM_NEWACTION on the two error paths; net->ct.labels_used is never released. The err: label is safe to reach from both sites: p->tmpl is still NULL there (kzalloc'd, not yet assigned) and nf_ct_put(NULL) is a no-op, so no inline release is needed. The Linux kernel CVE team has assigned CVE-2026-72430 to this issue. Affected and fixed versions =========================== Issue introduced in 6.7 with commit 70f06c115bcca26ceeebf938e48bc8143668e38b and fixed in 6.12.97 with commit 13b561c893c741635adce3781490a7a1099106c8 Issue introduced in 6.7 with commit 70f06c115bcca26ceeebf938e48bc8143668e38b and fixed in 6.18.40 with commit 1d51aff78f078af1a80e9496c2f4643f4c0ef0a0 Issue introduced in 6.7 with commit 70f06c115bcca26ceeebf938e48bc8143668e38b and fixed in 7.1.5 with commit 0c3d8fc87e10e38fe054ece009d6d1f66bef2cd4 Issue introduced in 6.7 with commit 70f06c115bcca26ceeebf938e48bc8143668e38b and fixed in 7.2-rc1 with commit 16e088016f38cf728a0de709c3335cc5a3850476 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-72430 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/sched/act_ct.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/13b561c893c741635adce3781490a7a1099106c8 https://git.kernel.org/stable/c/1d51aff78f078af1a80e9496c2f4643f4c0ef0a0 https://git.kernel.org/stable/c/0c3d8fc87e10e38fe054ece009d6d1f66bef2cd4 https://git.kernel.org/stable/c/16e088016f38cf728a0de709c3335cc5a3850476