<?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 07:54:29 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-71126</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-71126</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-71126</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0166 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-0166</link>
      <description>certfr-2026-avi-0166</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0166</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-71126</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-71126</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 137 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mptcp: avoid deadlock on fallback while reinjecting Jakub reported an MPTCP deadlock at fallback time:  WARNING: possible recursive locking detected  6.18.0-rc7-virtme #1 Not tainted  --------------------------------------------  mptcp_connect/20858 is trying to acquire lock:  ff1100001da18b60 (&amp;amp;msk-&amp;gt;fallback_lock){+.-.}-{3:3}, at: __mptcp_try_fallback+0xd8/0x280  but task is already holding lock:  ff1100001da18b60 (&amp;amp;msk-&amp;gt;fallback_lock){+.-.}-{3:3}, at: __mptcp_retrans+0x352/0xaa0  other info that might help us debug this:   Possible unsafe locking scenario:         CPU0         ----    lock(&amp;amp;msk-&amp;gt;fallback_lock);    lock(&amp;amp;msk-&amp;gt;fallback_lock);   *** DEADLOCK ***   May be due to missing lock nesting notation  3 locks held by mptcp_connect/20858:   #0: ff1100001da18290 (sk_lock-AF_INET){+.+.}-{0:0}, at: mptcp_sendmsg+0x114/0x1bc0   #1: ff1100001db40fd0 (k-sk_lock-AF_INET#2){+.+.}-{0:0}, at: __mptcp_retrans+0x2cb/0xaa0   #2: ff1100001da18b60 (&amp;amp;msk-&amp;gt;fallback_lock){+.-.}-{3:3}, at: __mptcp_retrans+0x352/0xaa0  stack backtrace:  CPU: 0 UID: 0 PID: 20858 Comm: mptcp_connect Not tainted 6.18.0-rc7-virtme #1 PREEMPT(full)  Hardware name: Bochs, BIOS Bochs 01/01/2011  Call Trace:   &amp;lt;TASK&amp;gt;   dump_stack_lvl+0x6f/0xa0   print_deadlock_bug.cold+0xc0/0xcd   validate_chain+0x2ff/0x5f0   __lock_acquire+0x34c/0x740   lock_acquire.part.0+0xbc/0x260   _raw_spin_lock_bh+0x38/0x50   __mptcp_try_fallback+0xd8/0x280   mptcp_sendmsg_…&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 137 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mptcp: avoid deadlock on fallback while reinjecting Jakub reported an MPTCP deadlock at fallback time:  WARNING: possible recursive locking detected  6.18.0-rc7-virtme #1 Not tainted  --------------------------------------------  mptcp_connect/20858 is trying to acquire lock:  ff1100001da18b60 (&amp;amp;msk-&amp;gt;fallback_lock){+.-.}-{3:3}, at: __mptcp_try_fallback+0xd8/0x280  but task is already holding lock:  ff1100001da18b60 (&amp;amp;msk-&amp;gt;fallback_lock){+.-.}-{3:3}, at: __mptcp_retrans+0x352/0xaa0  other info that might help us debug this:   Possible unsafe locking scenario:         CPU0         ----    lock(&amp;amp;msk-&amp;gt;fallback_lock);    lock(&amp;amp;msk-&amp;gt;fallback_lock);   *** DEADLOCK ***   May be due to missing lock nesting notation  3 locks held by mptcp_connect/20858:   #0: ff1100001da18290 (sk_lock-AF_INET){+.+.}-{0:0}, at: mptcp_sendmsg+0x114/0x1bc0   #1: ff1100001db40fd0 (k-sk_lock-AF_INET#2){+.+.}-{0:0}, at: __mptcp_retrans+0x2cb/0xaa0   #2: ff1100001da18b60 (&amp;amp;msk-&amp;gt;fallback_lock){+.-.}-{3:3}, at: __mptcp_retrans+0x352/0xaa0  stack backtrace:  CPU: 0 UID: 0 PID: 20858 Comm: mptcp_connect Not tainted 6.18.0-rc7-virtme #1 PREEMPT(full)  Hardware name: Bochs, BIOS Bochs 01/01/2011  Call Trace:   &amp;lt;TASK&amp;gt;   dump_stack_lvl+0x6f/0xa0   print_deadlock_bug.cold+0xc0/0xcd   validate_chain+0x2ff/0x5f0   __lock_acquire+0x34c/0x740   lock_acquire.part.0+0xbc/0x260   _raw_spin_lock_bh+0x38/0x50   __mptcp_try_fallback+0xd8/0x280   mptcp_sendmsg_…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-71126</guid>
    </item>
  </channel>
</rss>
