<?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, 07 Oct 2026 17:07:21 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-02852</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-02852</link>
      <description>bdu:2026-02852</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-02852</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-39674</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-39674</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2025-39674</guid>
    </item>
    <item>
      <title>EUVD-2026-314730</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-314730</link>
      <description>EUVD-2026-314730</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-314730</guid>
    </item>
    <item>
      <title>fkie_cve-2025-39674</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-39674</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;scsi: ufs: ufs-qcom: Fix ESI null pointer dereference&lt;/p&gt;
&lt;p&gt;ESI/MSI is a performance optimization feature that provides dedicated
interrupts per MCQ hardware queue. This is optional feature and UFS MCQ
should work with and without ESI feature.&lt;/p&gt;
&lt;p&gt;Commit e46a28cea29a (&amp;#34;scsi: ufs: qcom: Remove the MSI descriptor abuse&amp;#34;)
brings a regression in ESI (Enhanced System Interrupt) configuration that
causes a null pointer dereference when Platform MSI allocation fails.&lt;/p&gt;
&lt;p&gt;The issue occurs in when platform_device_msi_init_and_alloc_irqs() in
ufs_qcom_config_esi() fails (returns -EINVAL) but the current code uses
__free() macro for automatic cleanup free MSI resources that were never
successfully allocated.&lt;/p&gt;
&lt;p&gt;Unable to handle kernel NULL pointer dereference at virtual
address 0000000000000008&lt;/p&gt;
&lt;p&gt;Call trace:
  mutex_lock+0xc/0x54 (P)
  platform_device_msi_free_irqs_all+0x1c/0x40
  ufs_qcom_config_esi+0x1d0/0x220 [ufs_qcom]
  ufshcd_config_mcq+0x28/0x104
  ufshcd_init+0xa3c/0xf40
  ufshcd_pltfrm_init+0x504/0x7d4
  ufs_qcom_probe+0x20/0x58 [ufs_qcom]&lt;/p&gt;
&lt;p&gt;Fix by restructuring the ESI configuration to try MSI allocation first,
before any other resource allocation and instead use explicit cleanup
instead of __free() macro to avoid cleanup of unallocated resources.&lt;/p&gt;
&lt;p&gt;Tested on SM8750 platform with MCQ enabled, both with and without
Platform ESI support.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;scsi: ufs: ufs-qcom: Fix ESI null pointer dereference&lt;/p&gt;
&lt;p&gt;ESI/MSI is a performance optimization feature that provides dedicated
interrupts per MCQ hardware queue. This is optional feature and UFS MCQ
should work with and without ESI feature.&lt;/p&gt;
&lt;p&gt;Commit e46a28cea29a (&amp;#34;scsi: ufs: qcom: Remove the MSI descriptor abuse&amp;#34;)
brings a regression in ESI (Enhanced System Interrupt) configuration that
causes a null pointer dereference when Platform MSI allocation fails.&lt;/p&gt;
&lt;p&gt;The issue occurs in when platform_device_msi_init_and_alloc_irqs() in
ufs_qcom_config_esi() fails (returns -EINVAL) but the current code uses
__free() macro for automatic cleanup free MSI resources that were never
successfully allocated.&lt;/p&gt;
&lt;p&gt;Unable to handle kernel NULL pointer dereference at virtual
address 0000000000000008&lt;/p&gt;
&lt;p&gt;Call trace:
  mutex_lock+0xc/0x54 (P)
  platform_device_msi_free_irqs_all+0x1c/0x40
  ufs_qcom_config_esi+0x1d0/0x220 [ufs_qcom]
  ufshcd_config_mcq+0x28/0x104
  ufshcd_init+0xa3c/0xf40
  ufshcd_pltfrm_init+0x504/0x7d4
  ufs_qcom_probe+0x20/0x58 [ufs_qcom]&lt;/p&gt;
&lt;p&gt;Fix by restructuring the ESI configuration to try MSI allocation first,
before any other resource allocation and instead use explicit cleanup
instead of __free() macro to avoid cleanup of unallocated resources.&lt;/p&gt;
&lt;p&gt;Tested on SM8750 platform with MCQ enabled, both with and without
Platform ESI support.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-39674</guid>
    </item>
    <item>
      <title>GHSA-mg6h-9rrq-3f7m</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-mg6h-9rrq-3f7m</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;scsi: ufs: ufs-qcom: Fix ESI null pointer dereference&lt;/p&gt;
&lt;p&gt;ESI/MSI is a performance optimization feature that provides dedicated
interrupts per MCQ hardware queue. This is optional feature and UFS MCQ
should work with and without ESI feature.&lt;/p&gt;
&lt;p&gt;Commit e46a28cea29a (&amp;#34;scsi: ufs: qcom: Remove the MSI descriptor abuse&amp;#34;)
brings a regression in ESI (Enhanced System Interrupt) configuration that
causes a null pointer dereference when Platform MSI allocation fails.&lt;/p&gt;
&lt;p&gt;The issue occurs in when platform_device_msi_init_and_alloc_irqs() in
ufs_qcom_config_esi() fails (returns -EINVAL) but the current code uses
__free() macro for automatic cleanup free MSI resources that were never
successfully allocated.&lt;/p&gt;
&lt;p&gt;Unable to handle kernel NULL pointer dereference at virtual
address 0000000000000008&lt;/p&gt;
&lt;p&gt;Call trace:
  mutex_lock+0xc/0x54 (P)
  platform_device_msi_free_irqs_all+0x1c/0x40
  ufs_qcom_config_esi+0x1d0/0x220 [ufs_qcom]
  ufshcd_config_mcq+0x28/0x104
  ufshcd_init+0xa3c/0xf40
  ufshcd_pltfrm_init+0x504/0x7d4
  ufs_qcom_probe+0x20/0x58 [ufs_qcom]&lt;/p&gt;
&lt;p&gt;Fix by restructuring the ESI configuration to try MSI allocation first,
before any other resource allocation and instead use explicit cleanup
instead of __free() macro to avoid cleanup of unallocated resources.&lt;/p&gt;
&lt;p&gt;Tested on SM8750 platform with MCQ enabled, both with and without
Platform ESI support.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;scsi: ufs: ufs-qcom: Fix ESI null pointer dereference&lt;/p&gt;
&lt;p&gt;ESI/MSI is a performance optimization feature that provides dedicated
interrupts per MCQ hardware queue. This is optional feature and UFS MCQ
should work with and without ESI feature.&lt;/p&gt;
&lt;p&gt;Commit e46a28cea29a (&amp;#34;scsi: ufs: qcom: Remove the MSI descriptor abuse&amp;#34;)
brings a regression in ESI (Enhanced System Interrupt) configuration that
causes a null pointer dereference when Platform MSI allocation fails.&lt;/p&gt;
&lt;p&gt;The issue occurs in when platform_device_msi_init_and_alloc_irqs() in
ufs_qcom_config_esi() fails (returns -EINVAL) but the current code uses
__free() macro for automatic cleanup free MSI resources that were never
successfully allocated.&lt;/p&gt;
&lt;p&gt;Unable to handle kernel NULL pointer dereference at virtual
address 0000000000000008&lt;/p&gt;
&lt;p&gt;Call trace:
  mutex_lock+0xc/0x54 (P)
  platform_device_msi_free_irqs_all+0x1c/0x40
  ufs_qcom_config_esi+0x1d0/0x220 [ufs_qcom]
  ufshcd_config_mcq+0x28/0x104
  ufshcd_init+0xa3c/0xf40
  ufshcd_pltfrm_init+0x504/0x7d4
  ufs_qcom_probe+0x20/0x58 [ufs_qcom]&lt;/p&gt;
&lt;p&gt;Fix by restructuring the ESI configuration to try MSI allocation first,
before any other resource allocation and instead use explicit cleanup
instead of __free() macro to avoid cleanup of unallocated resources.&lt;/p&gt;
&lt;p&gt;Tested on SM8750 platform with MCQ enabled, both with and without
Platform ESI support.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-mg6h-9rrq-3f7m</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-39674</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-39674</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 77 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: scsi: ufs: ufs-qcom: Fix ESI null pointer dereference ESI/MSI is a performance optimization feature that provides dedicated interrupts per MCQ hardware queue. This is optional feature and UFS MCQ should work with and without ESI feature. Commit e46a28cea29a (&amp;#34;scsi: ufs: qcom: Remove the MSI descriptor abuse&amp;#34;) brings a regression in ESI (Enhanced System Interrupt) configuration that causes a null pointer dereference when Platform MSI allocation fails. The issue occurs in when platform_device_msi_init_and_alloc_irqs() in ufs_qcom_config_esi() fails (returns -EINVAL) but the current code uses __free() macro for automatic cleanup free MSI resources that were never successfully allocated. Unable to handle kernel NULL pointer dereference at virtual address 0000000000000008   Call trace:   mutex_lock+0xc/0x54 (P)   platform_device_msi_free_irqs_all+0x1c/0x40   ufs_qcom_config_esi+0x1d0/0x220 [ufs_qcom]   ufshcd_config_mcq+0x28/0x104   ufshcd_init+0xa3c/0xf40   ufshcd_pltfrm_init+0x504/0x7d4   ufs_qcom_probe+0x20/0x58 [ufs_qcom] Fix by restructuring the ESI configuration to try MSI allocation first, before any other resource allocation and instead use explicit cleanup instead of __free() macro to avoid cleanup of unallocated resources. Tested on SM8750 platform with MCQ enabled, both with and without Platform ESI support.&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 77 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: scsi: ufs: ufs-qcom: Fix ESI null pointer dereference ESI/MSI is a performance optimization feature that provides dedicated interrupts per MCQ hardware queue. This is optional feature and UFS MCQ should work with and without ESI feature. Commit e46a28cea29a (&amp;#34;scsi: ufs: qcom: Remove the MSI descriptor abuse&amp;#34;) brings a regression in ESI (Enhanced System Interrupt) configuration that causes a null pointer dereference when Platform MSI allocation fails. The issue occurs in when platform_device_msi_init_and_alloc_irqs() in ufs_qcom_config_esi() fails (returns -EINVAL) but the current code uses __free() macro for automatic cleanup free MSI resources that were never successfully allocated. Unable to handle kernel NULL pointer dereference at virtual address 0000000000000008   Call trace:   mutex_lock+0xc/0x54 (P)   platform_device_msi_free_irqs_all+0x1c/0x40   ufs_qcom_config_esi+0x1d0/0x220 [ufs_qcom]   ufshcd_config_mcq+0x28/0x104   ufshcd_init+0xa3c/0xf40   ufshcd_pltfrm_init+0x504/0x7d4   ufs_qcom_probe+0x20/0x58 [ufs_qcom] Fix by restructuring the ESI configuration to try MSI allocation first, before any other resource allocation and instead use explicit cleanup instead of __free() macro to avoid cleanup of unallocated resources. Tested on SM8750 platform with MCQ enabled, both with and without Platform ESI support.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-39674</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-1988 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1988</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher spezifizierte Auswirkungen zu erzielen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher spezifizierte Auswirkungen zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1988</guid>
    </item>
  </channel>
</rss>
