<?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>Fri, 02 Oct 2026 15:48:45 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-21958 — Revert "openvswitch: switch to per-action label counting in conntrack"</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-21958</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;Revert &amp;#34;openvswitch: switch to per-action label counting in conntrack&amp;#34;&lt;/p&gt;
&lt;p&gt;Currently, ovs_ct_set_labels() is only called for confirmed conntrack
entries (ct) within ovs_ct_commit(). However, if the conntrack entry
does not have the labels_ext extension, attempting to allocate it in
ovs_ct_get_conn_labels() for a confirmed entry triggers a warning in
nf_ct_ext_add():&lt;/p&gt;
&lt;p&gt;WARN_ON(nf_ct_is_confirmed(ct));&lt;/p&gt;
&lt;p&gt;This happens when the conntrack entry is created externally before OVS
increments net-&amp;gt;ct.labels_used. The issue has become more likely since
commit fcb1aa5163b1 (&amp;#34;openvswitch: switch to per-action label counting
in conntrack&amp;#34;), which changed to use per-action label counting and
increment net-&amp;gt;ct.labels_used when a flow with ct action is added.&lt;/p&gt;
&lt;p&gt;Since there’s no straightforward way to fully resolve this issue at the
moment, this reverts the commit to avoid breaking existing use cases.&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;Revert &amp;#34;openvswitch: switch to per-action label counting in conntrack&amp;#34;&lt;/p&gt;
&lt;p&gt;Currently, ovs_ct_set_labels() is only called for confirmed conntrack
entries (ct) within ovs_ct_commit(). However, if the conntrack entry
does not have the labels_ext extension, attempting to allocate it in
ovs_ct_get_conn_labels() for a confirmed entry triggers a warning in
nf_ct_ext_add():&lt;/p&gt;
&lt;p&gt;WARN_ON(nf_ct_is_confirmed(ct));&lt;/p&gt;
&lt;p&gt;This happens when the conntrack entry is created externally before OVS
increments net-&amp;gt;ct.labels_used. The issue has become more likely since
commit fcb1aa5163b1 (&amp;#34;openvswitch: switch to per-action label counting
in conntrack&amp;#34;), which changed to use per-action label counting and
increment net-&amp;gt;ct.labels_used when a flow with ct action is added.&lt;/p&gt;
&lt;p&gt;Since there’s no straightforward way to fully resolve this issue at the
moment, this reverts the commit to avoid breaking existing use cases.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-21958</guid>
    </item>
  </channel>
</rss>
