<?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 10:35:22 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-21809</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-21809</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://127.0.0.1:10001/vuln/bell-cve-2025-21809</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0625 — De multiples vulnérabilités ont été découvertes dans Ubuntu Ubuntu. Certaines d'entre elles permettent à un attaquant d…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-0625</link>
      <description>certfr-2025-avi-0625</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0625</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-21809</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-21809</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 106 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: rxrpc, afs: Fix peer hash locking vs RCU callback In its address list, afs now retains pointers to and refs on one or more rxrpc_peer objects.  The address list is freed under RCU and at this time, it puts the refs on those peers. Now, when an rxrpc_peer object runs out of refs, it gets removed from the peer hash table and, for that, rxrpc has to take a spinlock.  However, it is now being called from afs&amp;#39;s RCU cleanup, which takes place in BH context - but it is just taking an ordinary spinlock. The put may also be called from non-BH context, and so there exists the possibility of deadlock if the BH-based RCU cleanup happens whilst the hash spinlock is held.  This led to the attached lockdep complaint. Fix this by changing spinlocks of rxnet-&amp;gt;peer_hash_lock back to BH-disabling locks.     ================================     WARNING: inconsistent lock state     6.13.0-rc5-build2+ #1223 Tainted: G            E     --------------------------------     inconsistent {SOFTIRQ-ON-W} -&amp;gt; {IN-SOFTIRQ-W} usage.     swapper/1/0 [HC0[0]:SC1[1]:HE1:SE0] takes:     ffff88810babe228 (&amp;amp;rxnet-&amp;gt;peer_hash_lock){+.?.}-{3:3}, at: rxrpc_put_peer+0xcb/0x180     {SOFTIRQ-ON-W} state was registered at:       mark_usage+0x164/0x180       __lock_acquire+0x544/0x990       lock_acquire.part.0+0x103/0x280       _raw_spin_lock+0x2f/0x40       rxrpc_peer_keepalive_worker+0x144/0x440       process_one_work+0x486/0x7c0       process_schedule…&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 106 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: rxrpc, afs: Fix peer hash locking vs RCU callback In its address list, afs now retains pointers to and refs on one or more rxrpc_peer objects.  The address list is freed under RCU and at this time, it puts the refs on those peers. Now, when an rxrpc_peer object runs out of refs, it gets removed from the peer hash table and, for that, rxrpc has to take a spinlock.  However, it is now being called from afs&amp;#39;s RCU cleanup, which takes place in BH context - but it is just taking an ordinary spinlock. The put may also be called from non-BH context, and so there exists the possibility of deadlock if the BH-based RCU cleanup happens whilst the hash spinlock is held.  This led to the attached lockdep complaint. Fix this by changing spinlocks of rxnet-&amp;gt;peer_hash_lock back to BH-disabling locks.     ================================     WARNING: inconsistent lock state     6.13.0-rc5-build2+ #1223 Tainted: G            E     --------------------------------     inconsistent {SOFTIRQ-ON-W} -&amp;gt; {IN-SOFTIRQ-W} usage.     swapper/1/0 [HC0[0]:SC1[1]:HE1:SE0] takes:     ffff88810babe228 (&amp;amp;rxnet-&amp;gt;peer_hash_lock){+.?.}-{3:3}, at: rxrpc_put_peer+0xcb/0x180     {SOFTIRQ-ON-W} state was registered at:       mark_usage+0x164/0x180       __lock_acquire+0x544/0x990       lock_acquire.part.0+0x103/0x280       _raw_spin_lock+0x2f/0x40       rxrpc_peer_keepalive_worker+0x144/0x440       process_one_work+0x486/0x7c0       process_schedule…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-21809</guid>
    </item>
  </channel>
</rss>
