<?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 18:21:45 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-07828</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-07828</link>
      <description>bdu:2024-07828</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-07828</guid>
    </item>
    <item>
      <title>BELL-CVE-2023-52516</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2023-52516</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-52516</guid>
    </item>
    <item>
      <title>certfr-2025-avi-1057 — De multiples vulnérabilités ont été découvertes dans les produits VMware. Elles permettent à un attaquant de provoquer…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-1057</link>
      <description>certfr-2025-avi-1057</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-1057</guid>
    </item>
    <item>
      <title>EUVD-2026-311548</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-311548</link>
      <description>EUVD-2026-311548</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-311548</guid>
    </item>
    <item>
      <title>fkie_cve-2023-52516</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-52516</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;dma-debug: don&amp;#39;t call __dma_entry_alloc_check_leak() under free_entries_lock&lt;/p&gt;
&lt;p&gt;__dma_entry_alloc_check_leak() calls into printk -&amp;gt; serial console
output (qcom geni) and grabs port-&amp;gt;lock under free_entries_lock
spin lock, which is a reverse locking dependency chain as qcom_geni
IRQ handler can call into dma-debug code and grab free_entries_lock
under port-&amp;gt;lock.&lt;/p&gt;
&lt;p&gt;Move __dma_entry_alloc_check_leak() call out of free_entries_lock
scope so that we don&amp;#39;t acquire serial console&amp;#39;s port-&amp;gt;lock under it.&lt;/p&gt;
&lt;p&gt;Trimmed-down lockdep splat:&lt;/p&gt;
&lt;p&gt;The existing dependency chain (in reverse order) is:&lt;/p&gt;
&lt;p&gt;-&amp;gt; #2 (free_entries_lock){-.-.}-{2:2}:
        _raw_spin_lock_irqsave+0x60/0x80
        dma_entry_alloc+0x38/0x110
        debug_dma_map_page+0x60/0xf8
        dma_map_page_attrs+0x1e0/0x230
        dma_map_single_attrs.constprop.0+0x6c/0xc8
        geni_se_rx_dma_prep+0x40/0xcc
        qcom_geni_serial_isr+0x310/0x510
        __handle_irq_event_percpu+0x110/0x244
        handle_irq_event_percpu+0x20/0x54
        handle_irq_event+0x50/0x88
        handle_fasteoi_irq+0xa4/0xcc
        handle_irq_desc+0x28/0x40
        generic_handle_domain_irq+0x24/0x30
        gic_handle_irq+0xc4/0x148
        do_interrupt_handler+0xa4/0xb0
        el1_interrupt+0x34/0x64
        el1h_64_irq_handler+0x18/0x24
        el1h_64_irq+0x64/0x68
        arch_local_irq_enable+0x4/0x8
        ____do_softirq+0x18/0x24
        ...…&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;dma-debug: don&amp;#39;t call __dma_entry_alloc_check_leak() under free_entries_lock&lt;/p&gt;
&lt;p&gt;__dma_entry_alloc_check_leak() calls into printk -&amp;gt; serial console
output (qcom geni) and grabs port-&amp;gt;lock under free_entries_lock
spin lock, which is a reverse locking dependency chain as qcom_geni
IRQ handler can call into dma-debug code and grab free_entries_lock
under port-&amp;gt;lock.&lt;/p&gt;
&lt;p&gt;Move __dma_entry_alloc_check_leak() call out of free_entries_lock
scope so that we don&amp;#39;t acquire serial console&amp;#39;s port-&amp;gt;lock under it.&lt;/p&gt;
&lt;p&gt;Trimmed-down lockdep splat:&lt;/p&gt;
&lt;p&gt;The existing dependency chain (in reverse order) is:&lt;/p&gt;
&lt;p&gt;-&amp;gt; #2 (free_entries_lock){-.-.}-{2:2}:
        _raw_spin_lock_irqsave+0x60/0x80
        dma_entry_alloc+0x38/0x110
        debug_dma_map_page+0x60/0xf8
        dma_map_page_attrs+0x1e0/0x230
        dma_map_single_attrs.constprop.0+0x6c/0xc8
        geni_se_rx_dma_prep+0x40/0xcc
        qcom_geni_serial_isr+0x310/0x510
        __handle_irq_event_percpu+0x110/0x244
        handle_irq_event_percpu+0x20/0x54
        handle_irq_event+0x50/0x88
        handle_fasteoi_irq+0xa4/0xcc
        handle_irq_desc+0x28/0x40
        generic_handle_domain_irq+0x24/0x30
        gic_handle_irq+0xc4/0x148
        do_interrupt_handler+0xa4/0xb0
        el1_interrupt+0x34/0x64
        el1h_64_irq_handler+0x18/0x24
        el1h_64_irq+0x64/0x68
        arch_local_irq_enable+0x4/0x8
        ____do_softirq+0x18/0x24
        ...…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-52516</guid>
    </item>
    <item>
      <title>GHSA-4jr3-hwqp-2vq3</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-4jr3-hwqp-2vq3</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;dma-debug: don&amp;#39;t call __dma_entry_alloc_check_leak() under free_entries_lock&lt;/p&gt;
&lt;p&gt;__dma_entry_alloc_check_leak() calls into printk -&amp;gt; serial console
output (qcom geni) and grabs port-&amp;gt;lock under free_entries_lock
spin lock, which is a reverse locking dependency chain as qcom_geni
IRQ handler can call into dma-debug code and grab free_entries_lock
under port-&amp;gt;lock.&lt;/p&gt;
&lt;p&gt;Move __dma_entry_alloc_check_leak() call out of free_entries_lock
scope so that we don&amp;#39;t acquire serial console&amp;#39;s port-&amp;gt;lock under it.&lt;/p&gt;
&lt;p&gt;Trimmed-down lockdep splat:&lt;/p&gt;
&lt;p&gt;The existing dependency chain (in reverse order) is:&lt;/p&gt;
&lt;p&gt;-&amp;gt; #2 (free_entries_lock){-.-.}-{2:2}:
        _raw_spin_lock_irqsave+0x60/0x80
        dma_entry_alloc+0x38/0x110
        debug_dma_map_page+0x60/0xf8
        dma_map_page_attrs+0x1e0/0x230
        dma_map_single_attrs.constprop.0+0x6c/0xc8
        geni_se_rx_dma_prep+0x40/0xcc
        qcom_geni_serial_isr+0x310/0x510
        __handle_irq_event_percpu+0x110/0x244
        handle_irq_event_percpu+0x20/0x54
        handle_irq_event+0x50/0x88
        handle_fasteoi_irq+0xa4/0xcc
        handle_irq_desc+0x28/0x40
        generic_handle_domain_irq+0x24/0x30
        gic_handle_irq+0xc4/0x148
        do_interrupt_handler+0xa4/0xb0
        el1_interrupt+0x34/0x64
        el1h_64_irq_handler+0x18/0x24
        el1h_64_irq+0x64/0x68
        arch_local_irq_enable+0x4/0x8
        ____do_softirq+0x18/0x24
        ...…&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;dma-debug: don&amp;#39;t call __dma_entry_alloc_check_leak() under free_entries_lock&lt;/p&gt;
&lt;p&gt;__dma_entry_alloc_check_leak() calls into printk -&amp;gt; serial console
output (qcom geni) and grabs port-&amp;gt;lock under free_entries_lock
spin lock, which is a reverse locking dependency chain as qcom_geni
IRQ handler can call into dma-debug code and grab free_entries_lock
under port-&amp;gt;lock.&lt;/p&gt;
&lt;p&gt;Move __dma_entry_alloc_check_leak() call out of free_entries_lock
scope so that we don&amp;#39;t acquire serial console&amp;#39;s port-&amp;gt;lock under it.&lt;/p&gt;
&lt;p&gt;Trimmed-down lockdep splat:&lt;/p&gt;
&lt;p&gt;The existing dependency chain (in reverse order) is:&lt;/p&gt;
&lt;p&gt;-&amp;gt; #2 (free_entries_lock){-.-.}-{2:2}:
        _raw_spin_lock_irqsave+0x60/0x80
        dma_entry_alloc+0x38/0x110
        debug_dma_map_page+0x60/0xf8
        dma_map_page_attrs+0x1e0/0x230
        dma_map_single_attrs.constprop.0+0x6c/0xc8
        geni_se_rx_dma_prep+0x40/0xcc
        qcom_geni_serial_isr+0x310/0x510
        __handle_irq_event_percpu+0x110/0x244
        handle_irq_event_percpu+0x20/0x54
        handle_irq_event+0x50/0x88
        handle_fasteoi_irq+0xa4/0xcc
        handle_irq_desc+0x28/0x40
        generic_handle_domain_irq+0x24/0x30
        gic_handle_irq+0xc4/0x148
        do_interrupt_handler+0xa4/0xb0
        el1_interrupt+0x34/0x64
        el1h_64_irq_handler+0x18/0x24
        el1h_64_irq+0x64/0x68
        arch_local_irq_enable+0x4/0x8
        ____do_softirq+0x18/0x24
        ...…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-4jr3-hwqp-2vq3</guid>
    </item>
    <item>
      <title>gsd-2023-52516</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-52516</link>
      <description>gsd-2023-52516</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-52516</guid>
    </item>
    <item>
      <title>OESA-2024-1485 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-1485</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS: 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;
uio_hv_generic: Fix another memory leak in error handling paths&#13;
&#13;
Memory allocated by &amp;amp;apos;vmbus_alloc_ring()&amp;amp;apos; at the beginning of the probe
function is never freed in the error handling path.&#13;
&#13;
Add the missing &amp;amp;apos;vmbus_free_ring()&amp;amp;apos; call.&#13;
&#13;
Note that it is already freed in the .remove function.(CVE-2021-47070)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
asix: fix uninit-value in asix_mdio_read()&#13;
&#13;
asix_read_cmd() may read less than sizeof(smsr) bytes and in this case
smsr will be uninitialized.&#13;
&#13;
Fail log:
BUG: KMSAN: uninit-value in asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline]
BUG: KMSAN: uninit-value in asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline] drivers/net/usb/asix_common.c:497
BUG: KMSAN: uninit-value in asix_mdio_read+0x3c1/0xb00 drivers/net/usb/asix_common.c:497 drivers/net/usb/asix_common.c:497
 asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline]
 asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline] drivers/net/usb/asix_common.c:497
 asix_mdio_read+0x3c1/0xb00 drivers/net/usb/asix_common.c:497 drivers/net/usb/asix_common.c:497(CVE-2021-47101)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
EDAC/thunderx: Fix possible out-of-bounds string access&#13;
&#13;
Enabling -Wstringop-overflow globally…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS: 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;
uio_hv_generic: Fix another memory leak in error handling paths&#13;
&#13;
Memory allocated by &amp;amp;apos;vmbus_alloc_ring()&amp;amp;apos; at the beginning of the probe
function is never freed in the error handling path.&#13;
&#13;
Add the missing &amp;amp;apos;vmbus_free_ring()&amp;amp;apos; call.&#13;
&#13;
Note that it is already freed in the .remove function.(CVE-2021-47070)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
asix: fix uninit-value in asix_mdio_read()&#13;
&#13;
asix_read_cmd() may read less than sizeof(smsr) bytes and in this case
smsr will be uninitialized.&#13;
&#13;
Fail log:
BUG: KMSAN: uninit-value in asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline]
BUG: KMSAN: uninit-value in asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline] drivers/net/usb/asix_common.c:497
BUG: KMSAN: uninit-value in asix_mdio_read+0x3c1/0xb00 drivers/net/usb/asix_common.c:497 drivers/net/usb/asix_common.c:497
 asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline]
 asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline] drivers/net/usb/asix_common.c:497
 asix_mdio_read+0x3c1/0xb00 drivers/net/usb/asix_common.c:497 drivers/net/usb/asix_common.c:497(CVE-2021-47101)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
EDAC/thunderx: Fix possible out-of-bounds string access&#13;
&#13;
Enabling -Wstringop-overflow globally…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-1485</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-52516</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-52516</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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 129 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: dma-debug: don&amp;#39;t call __dma_entry_alloc_check_leak() under free_entries_lock __dma_entry_alloc_check_leak() calls into printk -&amp;gt; serial console output (qcom geni) and grabs port-&amp;gt;lock under free_entries_lock spin lock, which is a reverse locking dependency chain as qcom_geni IRQ handler can call into dma-debug code and grab free_entries_lock under port-&amp;gt;lock. Move __dma_entry_alloc_check_leak() call out of free_entries_lock scope so that we don&amp;#39;t acquire serial console&amp;#39;s port-&amp;gt;lock under it. Trimmed-down lockdep splat:  The existing dependency chain (in reverse order) is:                -&amp;gt; #2 (free_entries_lock){-.-.}-{2:2}:         _raw_spin_lock_irqsave+0x60/0x80         dma_entry_alloc+0x38/0x110         debug_dma_map_page+0x60/0xf8         dma_map_page_attrs+0x1e0/0x230         dma_map_single_attrs.constprop.0+0x6c/0xc8         geni_se_rx_dma_prep+0x40/0xcc         qcom_geni_serial_isr+0x310/0x510         __handle_irq_event_percpu+0x110/0x244         handle_irq_event_percpu+0x20/0x54         handle_irq_event+0x50/0x88         handle_fasteoi_irq+0xa4/0xcc         handle_irq_desc+0x28/0x40         generic_handle_domain_irq+0x24/0x30         gic_handle_irq+0xc4/0x148         do_interrupt_handler+0xa4/0xb0         el1_interrupt+0x34/0x64         el1h_64_irq_handler+0x18/0x24         el1h_64_irq+0x64/0x68         arch_local_irq_enable+0x4/0x8         ____do_softirq+0x18/0x24         ...                -&amp;gt; #1 (…&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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 129 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: dma-debug: don&amp;#39;t call __dma_entry_alloc_check_leak() under free_entries_lock __dma_entry_alloc_check_leak() calls into printk -&amp;gt; serial console output (qcom geni) and grabs port-&amp;gt;lock under free_entries_lock spin lock, which is a reverse locking dependency chain as qcom_geni IRQ handler can call into dma-debug code and grab free_entries_lock under port-&amp;gt;lock. Move __dma_entry_alloc_check_leak() call out of free_entries_lock scope so that we don&amp;#39;t acquire serial console&amp;#39;s port-&amp;gt;lock under it. Trimmed-down lockdep splat:  The existing dependency chain (in reverse order) is:                -&amp;gt; #2 (free_entries_lock){-.-.}-{2:2}:         _raw_spin_lock_irqsave+0x60/0x80         dma_entry_alloc+0x38/0x110         debug_dma_map_page+0x60/0xf8         dma_map_page_attrs+0x1e0/0x230         dma_map_single_attrs.constprop.0+0x6c/0xc8         geni_se_rx_dma_prep+0x40/0xcc         qcom_geni_serial_isr+0x310/0x510         __handle_irq_event_percpu+0x110/0x244         handle_irq_event_percpu+0x20/0x54         handle_irq_event+0x50/0x88         handle_fasteoi_irq+0xa4/0xcc         handle_irq_desc+0x28/0x40         generic_handle_domain_irq+0x24/0x30         gic_handle_irq+0xc4/0x148         do_interrupt_handler+0xa4/0xb0         el1_interrupt+0x34/0x64         el1h_64_irq_handler+0x18/0x24         el1h_64_irq+0x64/0x68         arch_local_irq_enable+0x4/0x8         ____do_softirq+0x18/0x24         ...                -&amp;gt; #1 (…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-52516</guid>
    </item>
  </channel>
</rss>
