<?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>Fri, 20 Nov 2026 16:28:11 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-23143</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-23143</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, 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:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/bell-cve-2025-23143</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0559 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-0559</link>
      <description>certfr-2025-avi-0559</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0559</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-23143</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-23143</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 206 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: Fix null-ptr-deref by sock_lock_init_class_and_name() and rmmod. When I ran the repro [0] and waited a few seconds, I observed two LOCKDEP splats: a warning immediately followed by a null-ptr-deref. [1] Reproduction Steps:   1) Mount CIFS   2) Add an iptables rule to drop incoming FIN packets for CIFS   3) Unmount CIFS   4) Unload the CIFS module   5) Remove the iptables rule At step 3), the CIFS module calls sock_release() for the underlying TCP socket, and it returns quickly.  However, the socket remains in FIN_WAIT_1 because incoming FIN packets are dropped. At this point, the module&amp;#39;s refcnt is 0 while the socket is still alive, so the following rmmod command succeeds.   # ss -tan   State      Recv-Q Send-Q Local Address:Port  Peer Address:Port   FIN-WAIT-1 0      477        10.0.2.15:51062   10.0.0.137:445   # lsmod | grep cifs   cifs                 1159168  0 This highlights a discrepancy between the lifetime of the CIFS module and the underlying TCP socket.  Even after CIFS calls sock_release() and it returns, the TCP socket does not die immediately in order to close the connection gracefully. While this is generally fine, it causes an issue with LOCKDEP because CIFS assigns a different lock class to the TCP socket&amp;#39;s sk-&amp;gt;sk_lock using sock_lock_init_class_and_name(). Once an incoming packet is processed for the socket or a timer fires, sk-&amp;gt;sk_lock is acquired. Then, LOCKDEP checks the lock conte…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 206 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: Fix null-ptr-deref by sock_lock_init_class_and_name() and rmmod. When I ran the repro [0] and waited a few seconds, I observed two LOCKDEP splats: a warning immediately followed by a null-ptr-deref. [1] Reproduction Steps:   1) Mount CIFS   2) Add an iptables rule to drop incoming FIN packets for CIFS   3) Unmount CIFS   4) Unload the CIFS module   5) Remove the iptables rule At step 3), the CIFS module calls sock_release() for the underlying TCP socket, and it returns quickly.  However, the socket remains in FIN_WAIT_1 because incoming FIN packets are dropped. At this point, the module&amp;#39;s refcnt is 0 while the socket is still alive, so the following rmmod command succeeds.   # ss -tan   State      Recv-Q Send-Q Local Address:Port  Peer Address:Port   FIN-WAIT-1 0      477        10.0.2.15:51062   10.0.0.137:445   # lsmod | grep cifs   cifs                 1159168  0 This highlights a discrepancy between the lifetime of the CIFS module and the underlying TCP socket.  Even after CIFS calls sock_release() and it returns, the TCP socket does not die immediately in order to close the connection gracefully. While this is generally fine, it causes an issue with LOCKDEP because CIFS assigns a different lock class to the TCP socket&amp;#39;s sk-&amp;gt;sk_lock using sock_lock_init_class_and_name(). Once an incoming packet is processed for the socket or a timer fires, sk-&amp;gt;sk_lock is acquired. Then, LOCKDEP checks the lock conte…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-23143</guid>
    </item>
  </channel>
</rss>
