<?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>Sun, 04 Oct 2026 07:23:18 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-15381</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-15381</link>
      <description>bdu:2025-15381</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-15381</guid>
    </item>
    <item>
      <title>BELL-CVE-2023-39180</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2023-39180</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: 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:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2023-39180</guid>
    </item>
    <item>
      <title>cnvd-2024-45871</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2024-45871</link>
      <description>cnvd-2024-45871</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2024-45871</guid>
    </item>
    <item>
      <title>EUVD-2026-202306</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-202306</link>
      <description>EUVD-2026-202306</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-202306</guid>
    </item>
    <item>
      <title>fkie_cve-2023-39180</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-39180</link>
      <description>&lt;p&gt;A flaw was found within the handling of SMB2_READ commands in the kernel ksmbd module. The issue results from not releasing memory after its effective lifetime. An attacker can leverage this to create a denial-of-service condition on affected installations of Linux. Authentication is not required to exploit this vulnerability, but only systems with ksmbd enabled are vulnerable.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A flaw was found within the handling of SMB2_READ commands in the kernel ksmbd module. The issue results from not releasing memory after its effective lifetime. An attacker can leverage this to create a denial-of-service condition on affected installations of Linux. Authentication is not required to exploit this vulnerability, but only systems with ksmbd enabled are vulnerable.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-39180</guid>
    </item>
    <item>
      <title>GHSA-9qrv-rvg6-cq37</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-9qrv-rvg6-cq37</link>
      <description>&lt;p&gt;A flaw was found within the handling of SMB2_READ commands in the kernel ksmbd module. The issue results from not releasing memory after its effective lifetime. An attacker can leverage this to create a denial-of-service condition on affected installations of Linux. Authentication is not required to exploit this vulnerability, but only systems with ksmbd enabled are vulnerable.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A flaw was found within the handling of SMB2_READ commands in the kernel ksmbd module. The issue results from not releasing memory after its effective lifetime. An attacker can leverage this to create a denial-of-service condition on affected installations of Linux. Authentication is not required to exploit this vulnerability, but only systems with ksmbd enabled are vulnerable.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-9qrv-rvg6-cq37</guid>
    </item>
    <item>
      <title>gsd-2023-39180</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-39180</link>
      <description>gsd-2023-39180</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-39180</guid>
    </item>
    <item>
      <title>OESA-2024-1765 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-1765</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP3: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
spi: Fix deadlock when adding SPI controllers on SPI buses&#13;
&#13;
Currently we have a global spi_add_lock which we take when adding new
devices so that we can check that we&amp;amp;apos;re not trying to reuse a chip
select that&amp;amp;apos;s already controlled.  This means that if the SPI device is
itself a SPI controller and triggers the instantiation of further SPI
devices we trigger a deadlock as we try to register and instantiate
those devices while in the process of doing so for the parent controller
and hence already holding the global spi_add_lock.  Since we only care
about concurrency within a single SPI bus move the lock to be per
controller, avoiding the deadlock.&#13;
&#13;
This can be easily triggered in the case of spi-mux.(CVE-2021-47469)&#13;
&#13;
(CVE-2023-39180)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
hid: cp2112: Fix duplicate workqueue initialization&#13;
&#13;
Previously the cp2112 driver called INIT_DELAYED_WORK within
cp2112_gpio_irq_startup, resulting in duplicate initilizations of the
workqueue on subsequent IRQ startups following an initial request. This
resulted in a warning in set_work_data in workqueue.c, as well as a rare
NULL dereference within process_one_work in workqueue.c.&#13;
&#13;
Initialize the workqueue within _probe instead.(CVE-2023-52853)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolv…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP3: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
spi: Fix deadlock when adding SPI controllers on SPI buses&#13;
&#13;
Currently we have a global spi_add_lock which we take when adding new
devices so that we can check that we&amp;amp;apos;re not trying to reuse a chip
select that&amp;amp;apos;s already controlled.  This means that if the SPI device is
itself a SPI controller and triggers the instantiation of further SPI
devices we trigger a deadlock as we try to register and instantiate
those devices while in the process of doing so for the parent controller
and hence already holding the global spi_add_lock.  Since we only care
about concurrency within a single SPI bus move the lock to be per
controller, avoiding the deadlock.&#13;
&#13;
This can be easily triggered in the case of spi-mux.(CVE-2021-47469)&#13;
&#13;
(CVE-2023-39180)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
hid: cp2112: Fix duplicate workqueue initialization&#13;
&#13;
Previously the cp2112 driver called INIT_DELAYED_WORK within
cp2112_gpio_irq_startup, resulting in duplicate initilizations of the
workqueue on subsequent IRQ startups following an initial request. This
resulted in a warning in set_work_data in workqueue.c, as well as a rare
NULL dereference within process_one_work in workqueue.c.&#13;
&#13;
Initialize the workqueue within _probe instead.(CVE-2023-52853)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolv…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-1765</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-39180</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-39180</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 159 more&lt;/p&gt;
&lt;p&gt;A flaw was found within the handling of SMB2_READ commands in the kernel ksmbd module. The issue results from not releasing memory after its effective lifetime. An attacker can leverage this to create a denial-of-service condition on affected installations of Linux. Authentication is not required to exploit this vulnerability, but only systems with ksmbd enabled are vulnerable.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 159 more&lt;/p&gt;
&lt;p&gt;A flaw was found within the handling of SMB2_READ commands in the kernel ksmbd module. The issue results from not releasing memory after its effective lifetime. An attacker can leverage this to create a denial-of-service condition on affected installations of Linux. Authentication is not required to exploit this vulnerability, but only systems with ksmbd enabled are vulnerable.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-39180</guid>
    </item>
  </channel>
</rss>
