<?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://cve.radiocsirt.org</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>Wed, 14 Oct 2026 21:15:22 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-35991 — dmaengine: idxd: Convert spinlock to mutex to lock evl workqueue</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-35991</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;dmaengine: idxd: Convert spinlock to mutex to lock evl workqueue&lt;/p&gt;
&lt;p&gt;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;&lt;/p&gt;
&lt;p&gt;The current implementation uses a spinlock to protect event log workqueue
and will lead to the Call Trace due to potential task rescheduling.&lt;/p&gt;
&lt;p&gt;To address the locking issue, convert the spinlock to mutex, allowing
the drain_workqueue() to be called in a safe mutex-locked context.&lt;/p&gt;
&lt;p&gt;This change ensures proper synchronization when accessing the event log
workqueue, preve…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;dmaengine: idxd: Convert spinlock to mutex to lock evl workqueue&lt;/p&gt;
&lt;p&gt;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;&lt;/p&gt;
&lt;p&gt;The current implementation uses a spinlock to protect event log workqueue
and will lead to the Call Trace due to potential task rescheduling.&lt;/p&gt;
&lt;p&gt;To address the locking issue, convert the spinlock to mutex, allowing
the drain_workqueue() to be called in a safe mutex-locked context.&lt;/p&gt;
&lt;p&gt;This change ensures proper synchronization when accessing the event log
workqueue, preve…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-35991</guid>
    </item>
    <item>
      <title>USN-6949-1 — linux, linux-aws, linux-gcp, linux-gke, linux-ibm, linux-nvidia, linux-nvidia-6.8 vulnerabilities</title>
      <link>https://cve.radiocsirt.org/vuln/usn-6949-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: linux-nvidia-6.8, Ubuntu:24.04:LTS: linux, Ubuntu:24.04:LTS: linux-aws, Ubuntu:24.04:LTS: linux-gcp, Ubuntu:24.04:LTS: linux-gke, Ubuntu:24.04:LTS: linux-ibm, Ubuntu:24.04:LTS: linux-nvidia&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM32 architecture;
  - ARM64 architecture;
  - M68K architecture;
  - OpenRISC architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Accessibility subsystem;
  - Bluetooth drivers;
  - Clock framework and drivers;
  - CPU frequency scaling framework;
  - Hardware crypto device drivers;
  - DMA engine subsystem;
  - DPLL subsystem;
  - FireWire subsystem;
  - EFI core;
  - Qualcomm firmware drivers;
  - GPIO subsystem;
  - GPU drivers;
  - Microsoft Hyper-V drivers;
  - InfiniBand drivers;
  - IOMMU subsystem;
  - IRQ chip drivers;
  - Macintosh device drivers;
  - Multiple devices driver;
  - Media drivers;
  - EEPROM drivers;
  - MMC subsystem;
  - Network drivers;
  - STMicroelectronics network drivers;
  - Device tree and open firmware driver;
  - HiSilicon SoC PMU drivers;
  - PHY drivers;
  - Pin controllers subsystem;
  - Remote Processor subsystem;
  - S/390 drivers;
  - SCSI drivers;
  - SPI subsystem;
  - Media staging drivers;
  - Thermal drivers;
  - Userspace I/O drivers;
  - USB subsystem;
  - DesignWare USB3 driver;
  - ACRN Hypervisor Service Module driver;
  - Virtio drivers;
  - 9P distributed file system;
  - BTRFS file system;
  - eCrypt file system;
  - EROFS file system;
  - File systems infrastructure;
  - GF…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: linux-nvidia-6.8, Ubuntu:24.04:LTS: linux, Ubuntu:24.04:LTS: linux-aws, Ubuntu:24.04:LTS: linux-gcp, Ubuntu:24.04:LTS: linux-gke, Ubuntu:24.04:LTS: linux-ibm, Ubuntu:24.04:LTS: linux-nvidia&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM32 architecture;
  - ARM64 architecture;
  - M68K architecture;
  - OpenRISC architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Accessibility subsystem;
  - Bluetooth drivers;
  - Clock framework and drivers;
  - CPU frequency scaling framework;
  - Hardware crypto device drivers;
  - DMA engine subsystem;
  - DPLL subsystem;
  - FireWire subsystem;
  - EFI core;
  - Qualcomm firmware drivers;
  - GPIO subsystem;
  - GPU drivers;
  - Microsoft Hyper-V drivers;
  - InfiniBand drivers;
  - IOMMU subsystem;
  - IRQ chip drivers;
  - Macintosh device drivers;
  - Multiple devices driver;
  - Media drivers;
  - EEPROM drivers;
  - MMC subsystem;
  - Network drivers;
  - STMicroelectronics network drivers;
  - Device tree and open firmware driver;
  - HiSilicon SoC PMU drivers;
  - PHY drivers;
  - Pin controllers subsystem;
  - Remote Processor subsystem;
  - S/390 drivers;
  - SCSI drivers;
  - SPI subsystem;
  - Media staging drivers;
  - Thermal drivers;
  - Userspace I/O drivers;
  - USB subsystem;
  - DesignWare USB3 driver;
  - ACRN Hypervisor Service Module driver;
  - Virtio drivers;
  - 9P distributed file system;
  - BTRFS file system;
  - eCrypt file system;
  - EROFS file system;
  - File systems infrastructure;
  - GF…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-6949-1</guid>
    </item>
  </channel>
</rss>
