<?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 01:47:26 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-35991</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-35991</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-2024-35991</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0526 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent une élé…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2024-avi-0526</link>
      <description>certfr-2024-avi-0526</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0526</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-35991</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-35991</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 88 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: Convert spinlock to mutex to lock evl workqueue drain_workqueue() cannot be called safely in a spinlocked context due to possible task rescheduling. In the multi-task scenario, calling queue_work() while drain_workqueue() will lead to a Call Trace as pushing a work on a draining workqueue is not permitted in spinlocked context.     Call Trace:     &amp;lt;TASK&amp;gt;     ? __warn+0x7d/0x140     ? __queue_work+0x2b2/0x440     ? report_bug+0x1f8/0x200     ? handle_bug+0x3c/0x70     ? exc_invalid_op+0x18/0x70     ? asm_exc_invalid_op+0x1a/0x20     ? __queue_work+0x2b2/0x440     queue_work_on+0x28/0x30     idxd_misc_thread+0x303/0x5a0 [idxd]     ? __schedule+0x369/0xb40     ? __pfx_irq_thread_fn+0x10/0x10     ? irq_thread+0xbc/0x1b0     irq_thread_fn+0x21/0x70     irq_thread+0x102/0x1b0     ? preempt_count_add+0x74/0xa0     ? __pfx_irq_thread_dtor+0x10/0x10     ? __pfx_irq_thread+0x10/0x10     kthread+0x103/0x140     ? __pfx_kthread+0x10/0x10     ret_from_fork+0x31/0x50     ? __pfx_kthread+0x10/0x10     ret_from_fork_asm+0x1b/0x30     &amp;lt;/TASK&amp;gt; The current implementation uses a spinlock to protect event log workqueue and will lead to the Call Trace due to potential task rescheduling. To address the locking issue, convert the spinlock to mutex, allowing the drain_workqueue() to be called in a safe mutex-locked context. This change ensures proper synchronization when accessing the event log workqueue, preventing…&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 88 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: Convert spinlock to mutex to lock evl workqueue drain_workqueue() cannot be called safely in a spinlocked context due to possible task rescheduling. In the multi-task scenario, calling queue_work() while drain_workqueue() will lead to a Call Trace as pushing a work on a draining workqueue is not permitted in spinlocked context.     Call Trace:     &amp;lt;TASK&amp;gt;     ? __warn+0x7d/0x140     ? __queue_work+0x2b2/0x440     ? report_bug+0x1f8/0x200     ? handle_bug+0x3c/0x70     ? exc_invalid_op+0x18/0x70     ? asm_exc_invalid_op+0x1a/0x20     ? __queue_work+0x2b2/0x440     queue_work_on+0x28/0x30     idxd_misc_thread+0x303/0x5a0 [idxd]     ? __schedule+0x369/0xb40     ? __pfx_irq_thread_fn+0x10/0x10     ? irq_thread+0xbc/0x1b0     irq_thread_fn+0x21/0x70     irq_thread+0x102/0x1b0     ? preempt_count_add+0x74/0xa0     ? __pfx_irq_thread_dtor+0x10/0x10     ? __pfx_irq_thread+0x10/0x10     kthread+0x103/0x140     ? __pfx_kthread+0x10/0x10     ret_from_fork+0x31/0x50     ? __pfx_kthread+0x10/0x10     ret_from_fork_asm+0x1b/0x30     &amp;lt;/TASK&amp;gt; The current implementation uses a spinlock to protect event log workqueue and will lead to the Call Trace due to potential task rescheduling. To address the locking issue, convert the spinlock to mutex, allowing the drain_workqueue() to be called in a safe mutex-locked context. This change ensures proper synchronization when accessing the event log workqueue, preventing…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-35991</guid>
    </item>
  </channel>
</rss>
