<?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 04:24:59 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-26775</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-26775</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-2024-26775</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0334 — De multiples vulnérabilités ont été découvertes dans &lt;span
class="textit"&gt;le noyau Linux de Debian&lt;/span&gt;. Elles permet…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2024-avi-0334</link>
      <description>certfr-2024-avi-0334</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0334</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-26775</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-26775</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 107 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: aoe: avoid potential deadlock at set_capacity Move set_capacity() outside of the section procected by (&amp;amp;d-&amp;gt;lock). To avoid possible interrupt unsafe locking scenario:         CPU0                    CPU1         ----                    ---- [1] lock(&amp;amp;bdev-&amp;gt;bd_size_lock);                                 local_irq_disable();                             [2] lock(&amp;amp;d-&amp;gt;lock);                             [3] lock(&amp;amp;bdev-&amp;gt;bd_size_lock);    &amp;lt;Interrupt&amp;gt; [4]  lock(&amp;amp;d-&amp;gt;lock);   *** DEADLOCK *** Where [1](&amp;amp;bdev-&amp;gt;bd_size_lock) hold by zram_add()-&amp;gt;set_capacity(). [2]lock(&amp;amp;d-&amp;gt;lock) hold by aoeblk_gdalloc(). And aoeblk_gdalloc() is trying to acquire [3](&amp;amp;bdev-&amp;gt;bd_size_lock) at set_capacity() call. In this situation an attempt to acquire [4]lock(&amp;amp;d-&amp;gt;lock) from aoecmd_cfg_rsp() will lead to deadlock. So the simplest solution is breaking lock dependency [2](&amp;amp;d-&amp;gt;lock) -&amp;gt; [3](&amp;amp;bdev-&amp;gt;bd_size_lock) by moving set_capacity() outside.&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 107 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: aoe: avoid potential deadlock at set_capacity Move set_capacity() outside of the section procected by (&amp;amp;d-&amp;gt;lock). To avoid possible interrupt unsafe locking scenario:         CPU0                    CPU1         ----                    ---- [1] lock(&amp;amp;bdev-&amp;gt;bd_size_lock);                                 local_irq_disable();                             [2] lock(&amp;amp;d-&amp;gt;lock);                             [3] lock(&amp;amp;bdev-&amp;gt;bd_size_lock);    &amp;lt;Interrupt&amp;gt; [4]  lock(&amp;amp;d-&amp;gt;lock);   *** DEADLOCK *** Where [1](&amp;amp;bdev-&amp;gt;bd_size_lock) hold by zram_add()-&amp;gt;set_capacity(). [2]lock(&amp;amp;d-&amp;gt;lock) hold by aoeblk_gdalloc(). And aoeblk_gdalloc() is trying to acquire [3](&amp;amp;bdev-&amp;gt;bd_size_lock) at set_capacity() call. In this situation an attempt to acquire [4]lock(&amp;amp;d-&amp;gt;lock) from aoecmd_cfg_rsp() will lead to deadlock. So the simplest solution is breaking lock dependency [2](&amp;amp;d-&amp;gt;lock) -&amp;gt; [3](&amp;amp;bdev-&amp;gt;bd_size_lock) by moving set_capacity() outside.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-26775</guid>
    </item>
  </channel>
</rss>
