<?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://cve.radiocsirt.org</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>Sun, 04 Oct 2026 09:35:04 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-12299</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-12299</link>
      <description>bdu:2025-12299</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-12299</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-21958</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-21958</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2025-21958</guid>
    </item>
    <item>
      <title>EUVD-2026-346722</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-346722</link>
      <description>EUVD-2026-346722</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-346722</guid>
    </item>
    <item>
      <title>fkie_cve-2025-21958</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-21958</link>
      <description>&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;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://cve.radiocsirt.org/vuln/fkie_cve-2025-21958</guid>
    </item>
    <item>
      <title>GHSA-jx6v-7wmg-pq67</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-jx6v-7wmg-pq67</link>
      <description>&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;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://cve.radiocsirt.org/vuln/ghsa-jx6v-7wmg-pq67</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-21958</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-21958</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 70 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Revert &amp;#34;openvswitch: switch to per-action label counting in conntrack&amp;#34; 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():   WARN_ON(nf_ct_is_confirmed(ct)); 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. 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; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 70 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Revert &amp;#34;openvswitch: switch to per-action label counting in conntrack&amp;#34; 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():   WARN_ON(nf_ct_is_confirmed(ct)); 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. 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://cve.radiocsirt.org/vuln/ubuntu-cve-2025-21958</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-0683 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0683</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial-of-Service auszulösen und um nicht näher spezifizierte Auswirkungen zu erzielen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial-of-Service auszulösen und um nicht näher spezifizierte Auswirkungen zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0683</guid>
    </item>
  </channel>
</rss>
