<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 13:41:01 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-72430 — net/sched: act_ct: fix nf_connlabels leak on two error paths</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-72430</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net/sched: act_ct: fix nf_connlabels leak on two error paths&lt;/p&gt;
&lt;p&gt;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 &amp;#34;goto err&amp;#34;, skipping the err: nf_connlabels_put() cleanup.
They also precede the &amp;#34;p-&amp;gt;put_labels = put_labels&amp;#34; 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-&amp;gt;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.&lt;/p&gt;
&lt;p&gt;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-&amp;gt;ct.labels_used is never
released.&lt;/p&gt;
&lt;p&gt;The err: label is safe to reach from both sites: p-&amp;gt;tmpl is still NULL
there (kzalloc&amp;#39;d, not yet assigned) and nf_ct_put(NULL) is a no-op, so
no inline release is needed.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net/sched: act_ct: fix nf_connlabels leak on two error paths&lt;/p&gt;
&lt;p&gt;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 &amp;#34;goto err&amp;#34;, skipping the err: nf_connlabels_put() cleanup.
They also precede the &amp;#34;p-&amp;gt;put_labels = put_labels&amp;#34; 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-&amp;gt;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.&lt;/p&gt;
&lt;p&gt;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-&amp;gt;ct.labels_used is never
released.&lt;/p&gt;
&lt;p&gt;The err: label is safe to reach from both sites: p-&amp;gt;tmpl is still NULL
there (kzalloc&amp;#39;d, not yet assigned) and nf_ct_put(NULL) is a no-op, so
no inline release is needed.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-72430</guid>
    </item>
  </channel>
</rss>
