<?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://127.0.0.1:10001</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>Sat, 21 Nov 2026 09:46:20 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-21865</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-21865</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/bell-cve-2025-21865</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0307 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-0307</link>
      <description>certfr-2025-avi-0307</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0307</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-21865</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-21865</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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 129 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: gtp: Suppress list corruption splat in gtp_net_exit_batch_rtnl(). Brad Spengler reported the list_del() corruption splat in gtp_net_exit_batch_rtnl(). [0] Commit eb28fd76c0a0 (&amp;#34;gtp: Destroy device along with udp socket&amp;#39;s netns dismantle.&amp;#34;) added the for_each_netdev() loop in gtp_net_exit_batch_rtnl() to destroy devices in each netns as done in geneve and ip tunnels. However, this could trigger -&amp;gt;dellink() twice for the same device during -&amp;gt;exit_batch_rtnl(). Say we have two netns A &amp;amp; B and gtp device B that resides in netns B but whose UDP socket is in netns A.   1. cleanup_net() processes netns A and then B.   2. gtp_net_exit_batch_rtnl() finds the device B while iterating      netns A&amp;#39;s gn-&amp;gt;gtp_dev_list and calls -&amp;gt;dellink().   [ device B is not yet unlinked from netns B     as unregister_netdevice_many() has not been called. ]   3. gtp_net_exit_batch_rtnl() finds the device B while iterating      netns B&amp;#39;s for_each_netdev() and calls -&amp;gt;dellink(). gtp_dellink() cleans up the device&amp;#39;s hash table, unlinks the dev from gn-&amp;gt;gtp_dev_list, and calls unregister_netdevice_queue(). Basically, calling gtp_dellink() multiple times is fine unless CONFIG_DEBUG_LIST is enabled. Let&amp;#39;s remove for_each_netdev() in gtp_net_exit_batch_rtnl() and delegate the destruction to default_device_exit_batch() as done in bareudp. [0]: list_del corruption, ffff8880aaa62c00-&amp;gt;next (autoslab_size_M_dev_P_net_core_dev_11127_8_1328_8_S_4096…&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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 129 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: gtp: Suppress list corruption splat in gtp_net_exit_batch_rtnl(). Brad Spengler reported the list_del() corruption splat in gtp_net_exit_batch_rtnl(). [0] Commit eb28fd76c0a0 (&amp;#34;gtp: Destroy device along with udp socket&amp;#39;s netns dismantle.&amp;#34;) added the for_each_netdev() loop in gtp_net_exit_batch_rtnl() to destroy devices in each netns as done in geneve and ip tunnels. However, this could trigger -&amp;gt;dellink() twice for the same device during -&amp;gt;exit_batch_rtnl(). Say we have two netns A &amp;amp; B and gtp device B that resides in netns B but whose UDP socket is in netns A.   1. cleanup_net() processes netns A and then B.   2. gtp_net_exit_batch_rtnl() finds the device B while iterating      netns A&amp;#39;s gn-&amp;gt;gtp_dev_list and calls -&amp;gt;dellink().   [ device B is not yet unlinked from netns B     as unregister_netdevice_many() has not been called. ]   3. gtp_net_exit_batch_rtnl() finds the device B while iterating      netns B&amp;#39;s for_each_netdev() and calls -&amp;gt;dellink(). gtp_dellink() cleans up the device&amp;#39;s hash table, unlinks the dev from gn-&amp;gt;gtp_dev_list, and calls unregister_netdevice_queue(). Basically, calling gtp_dellink() multiple times is fine unless CONFIG_DEBUG_LIST is enabled. Let&amp;#39;s remove for_each_netdev() in gtp_net_exit_batch_rtnl() and delegate the destruction to default_device_exit_batch() as done in bareudp. [0]: list_del corruption, ffff8880aaa62c00-&amp;gt;next (autoslab_size_M_dev_P_net_core_dev_11127_8_1328_8_S_4096…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-21865</guid>
    </item>
  </channel>
</rss>
