<?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>Sat, 03 Oct 2026 22:45:06 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-05936</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-05936</link>
      <description>bdu:2025-05936</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-05936</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-46847</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-46847</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://cve.radiocsirt.org/vuln/bell-cve-2024-46847</guid>
    </item>
    <item>
      <title>certfr-2024-avi-1080 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Elles permettent à un attaquant de provoq…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2024-avi-1080</link>
      <description>certfr-2024-avi-1080</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-1080</guid>
    </item>
    <item>
      <title>EUVD-2026-346144</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-346144</link>
      <description>EUVD-2026-346144</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-346144</guid>
    </item>
    <item>
      <title>fkie_cve-2024-46847</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-46847</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm: vmalloc: ensure vmap_block is initialised before adding to queue&lt;/p&gt;
&lt;p&gt;Commit 8c61291fd850 (&amp;#34;mm: fix incorrect vbq reference in
purge_fragmented_block&amp;#34;) extended the &amp;#39;vmap_block&amp;#39; structure to contain a
&amp;#39;cpu&amp;#39; field which is set at allocation time to the id of the initialising
CPU.&lt;/p&gt;
&lt;p&gt;When a new &amp;#39;vmap_block&amp;#39; is being instantiated by new_vmap_block(), the
partially initialised structure is added to the local &amp;#39;vmap_block_queue&amp;#39;
xarray before the &amp;#39;cpu&amp;#39; field has been initialised.  If another CPU is
concurrently walking the xarray (e.g.  via vm_unmap_aliases()), then it
may perform an out-of-bounds access to the remote queue thanks to an
uninitialised index.&lt;/p&gt;
&lt;p&gt;This has been observed as UBSAN errors in Android:&lt;/p&gt;
&lt;p&gt;| Internal error: UBSAN: array index out of bounds: 00000000f2005512 [#1] PREEMPT SMP
 |
 | Call trace:
 |  purge_fragmented_block+0x204/0x21c
 |  _vm_unmap_aliases+0x170/0x378
 |  vm_unmap_aliases+0x1c/0x28
 |  change_memory_common+0x1dc/0x26c
 |  set_memory_ro+0x18/0x24
 |  module_enable_ro+0x98/0x238
 |  do_init_module+0x1b0/0x310&lt;/p&gt;
&lt;p&gt;Move the initialisation of &amp;#39;vb-&amp;gt;cpu&amp;#39; in new_vmap_block() ahead of the
addition to the xarray.&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;mm: vmalloc: ensure vmap_block is initialised before adding to queue&lt;/p&gt;
&lt;p&gt;Commit 8c61291fd850 (&amp;#34;mm: fix incorrect vbq reference in
purge_fragmented_block&amp;#34;) extended the &amp;#39;vmap_block&amp;#39; structure to contain a
&amp;#39;cpu&amp;#39; field which is set at allocation time to the id of the initialising
CPU.&lt;/p&gt;
&lt;p&gt;When a new &amp;#39;vmap_block&amp;#39; is being instantiated by new_vmap_block(), the
partially initialised structure is added to the local &amp;#39;vmap_block_queue&amp;#39;
xarray before the &amp;#39;cpu&amp;#39; field has been initialised.  If another CPU is
concurrently walking the xarray (e.g.  via vm_unmap_aliases()), then it
may perform an out-of-bounds access to the remote queue thanks to an
uninitialised index.&lt;/p&gt;
&lt;p&gt;This has been observed as UBSAN errors in Android:&lt;/p&gt;
&lt;p&gt;| Internal error: UBSAN: array index out of bounds: 00000000f2005512 [#1] PREEMPT SMP
 |
 | Call trace:
 |  purge_fragmented_block+0x204/0x21c
 |  _vm_unmap_aliases+0x170/0x378
 |  vm_unmap_aliases+0x1c/0x28
 |  change_memory_common+0x1dc/0x26c
 |  set_memory_ro+0x18/0x24
 |  module_enable_ro+0x98/0x238
 |  do_init_module+0x1b0/0x310&lt;/p&gt;
&lt;p&gt;Move the initialisation of &amp;#39;vb-&amp;gt;cpu&amp;#39; in new_vmap_block() ahead of the
addition to the xarray.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-46847</guid>
    </item>
    <item>
      <title>GHSA-9r77-32hh-rxf4</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-9r77-32hh-rxf4</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm: vmalloc: ensure vmap_block is initialised before adding to queue&lt;/p&gt;
&lt;p&gt;Commit 8c61291fd850 (&amp;#34;mm: fix incorrect vbq reference in
purge_fragmented_block&amp;#34;) extended the &amp;#39;vmap_block&amp;#39; structure to contain a
&amp;#39;cpu&amp;#39; field which is set at allocation time to the id of the initialising
CPU.&lt;/p&gt;
&lt;p&gt;When a new &amp;#39;vmap_block&amp;#39; is being instantiated by new_vmap_block(), the
partially initialised structure is added to the local &amp;#39;vmap_block_queue&amp;#39;
xarray before the &amp;#39;cpu&amp;#39; field has been initialised.  If another CPU is
concurrently walking the xarray (e.g.  via vm_unmap_aliases()), then it
may perform an out-of-bounds access to the remote queue thanks to an
uninitialised index.&lt;/p&gt;
&lt;p&gt;This has been observed as UBSAN errors in Android:&lt;/p&gt;
&lt;p&gt;| Internal error: UBSAN: array index out of bounds: 00000000f2005512 [#1] PREEMPT SMP
 |
 | Call trace:
 |  purge_fragmented_block+0x204/0x21c
 |  _vm_unmap_aliases+0x170/0x378
 |  vm_unmap_aliases+0x1c/0x28
 |  change_memory_common+0x1dc/0x26c
 |  set_memory_ro+0x18/0x24
 |  module_enable_ro+0x98/0x238
 |  do_init_module+0x1b0/0x310&lt;/p&gt;
&lt;p&gt;Move the initialisation of &amp;#39;vb-&amp;gt;cpu&amp;#39; in new_vmap_block() ahead of the
addition to the xarray.&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;mm: vmalloc: ensure vmap_block is initialised before adding to queue&lt;/p&gt;
&lt;p&gt;Commit 8c61291fd850 (&amp;#34;mm: fix incorrect vbq reference in
purge_fragmented_block&amp;#34;) extended the &amp;#39;vmap_block&amp;#39; structure to contain a
&amp;#39;cpu&amp;#39; field which is set at allocation time to the id of the initialising
CPU.&lt;/p&gt;
&lt;p&gt;When a new &amp;#39;vmap_block&amp;#39; is being instantiated by new_vmap_block(), the
partially initialised structure is added to the local &amp;#39;vmap_block_queue&amp;#39;
xarray before the &amp;#39;cpu&amp;#39; field has been initialised.  If another CPU is
concurrently walking the xarray (e.g.  via vm_unmap_aliases()), then it
may perform an out-of-bounds access to the remote queue thanks to an
uninitialised index.&lt;/p&gt;
&lt;p&gt;This has been observed as UBSAN errors in Android:&lt;/p&gt;
&lt;p&gt;| Internal error: UBSAN: array index out of bounds: 00000000f2005512 [#1] PREEMPT SMP
 |
 | Call trace:
 |  purge_fragmented_block+0x204/0x21c
 |  _vm_unmap_aliases+0x170/0x378
 |  vm_unmap_aliases+0x1c/0x28
 |  change_memory_common+0x1dc/0x26c
 |  set_memory_ro+0x18/0x24
 |  module_enable_ro+0x98/0x238
 |  do_init_module+0x1b0/0x310&lt;/p&gt;
&lt;p&gt;Move the initialisation of &amp;#39;vb-&amp;gt;cpu&amp;#39; in new_vmap_block() ahead of the
addition to the xarray.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-9r77-32hh-rxf4</guid>
    </item>
    <item>
      <title>msrc_CVE-2024-46847 — mm: vmalloc: ensure vmap_block is initialised before adding to queue</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2024-46847</link>
      <description>msrc_CVE-2024-46847</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2024-46847</guid>
    </item>
    <item>
      <title>OESA-2025-1097 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-1097</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ksmbd: fix potencial out-of-bounds when buffer offset is invalid&lt;/p&gt;
&lt;p&gt;I found potencial out-of-bounds when buffer offset fields of a few requests
is invalid. This patch set the minimum value of buffer offset field to
-&amp;amp;gt;Buffer offset to validate buffer length.(CVE-2024-26952)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ksmbd: fix slab-out-of-bounds in smb_strndup_from_utf16()&lt;/p&gt;
&lt;p&gt;If -&amp;amp;gt;NameOffset of smb2_create_req is smaller than Buffer offset of
smb2_create_req, slab-out-of-bounds read can happen from smb2_open.
This patch set the minimum value of the name offset to the buffer offset
to validate name length of smb2_create_req().(CVE-2024-26954)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fpga: bridge: add owner module and take its refcount&lt;/p&gt;
&lt;p&gt;The current implementation of the fpga bridge assumes that the low-level
module registers a driver for the parent device and uses its owner pointer
to take the module&amp;amp;apos;s refcount. This approach is problematic since it can
lead to a null pointer dereference while attempting to get the bridge if
the parent device does not have a driver.&lt;/p&gt;
&lt;p&gt;To address this problem, add a module owner pointer to the fpga_bridge
struct and use it to take the module&amp;amp;apos;s refcount. Modify the function for
registering a bridge to take an additional owner module paramet…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ksmbd: fix potencial out-of-bounds when buffer offset is invalid&lt;/p&gt;
&lt;p&gt;I found potencial out-of-bounds when buffer offset fields of a few requests
is invalid. This patch set the minimum value of buffer offset field to
-&amp;amp;gt;Buffer offset to validate buffer length.(CVE-2024-26952)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ksmbd: fix slab-out-of-bounds in smb_strndup_from_utf16()&lt;/p&gt;
&lt;p&gt;If -&amp;amp;gt;NameOffset of smb2_create_req is smaller than Buffer offset of
smb2_create_req, slab-out-of-bounds read can happen from smb2_open.
This patch set the minimum value of the name offset to the buffer offset
to validate name length of smb2_create_req().(CVE-2024-26954)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fpga: bridge: add owner module and take its refcount&lt;/p&gt;
&lt;p&gt;The current implementation of the fpga bridge assumes that the low-level
module registers a driver for the parent device and uses its owner pointer
to take the module&amp;amp;apos;s refcount. This approach is problematic since it can
lead to a null pointer dereference while attempting to get the bridge if
the parent device does not have a driver.&lt;/p&gt;
&lt;p&gt;To address this problem, add a module owner pointer to the fpga_bridge
struct and use it to take the module&amp;amp;apos;s refcount. Modify the function for
registering a bridge to take an additional owner module paramet…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-1097</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-46847</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-46847</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 87 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mm: vmalloc: ensure vmap_block is initialised before adding to queue Commit 8c61291fd850 (&amp;#34;mm: fix incorrect vbq reference in purge_fragmented_block&amp;#34;) extended the &amp;#39;vmap_block&amp;#39; structure to contain a &amp;#39;cpu&amp;#39; field which is set at allocation time to the id of the initialising CPU. When a new &amp;#39;vmap_block&amp;#39; is being instantiated by new_vmap_block(), the partially initialised structure is added to the local &amp;#39;vmap_block_queue&amp;#39; xarray before the &amp;#39;cpu&amp;#39; field has been initialised.  If another CPU is concurrently walking the xarray (e.g.  via vm_unmap_aliases()), then it may perform an out-of-bounds access to the remote queue thanks to an uninitialised index. This has been observed as UBSAN errors in Android:  | Internal error: UBSAN: array index out of bounds: 00000000f2005512 [#1] PREEMPT SMP  |  | Call trace:  |  purge_fragmented_block+0x204/0x21c  |  _vm_unmap_aliases+0x170/0x378  |  vm_unmap_aliases+0x1c/0x28  |  change_memory_common+0x1dc/0x26c  |  set_memory_ro+0x18/0x24  |  module_enable_ro+0x98/0x238  |  do_init_module+0x1b0/0x310 Move the initialisation of &amp;#39;vb-&amp;gt;cpu&amp;#39; in new_vmap_block() ahead of the addition to the xarray.&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 87 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mm: vmalloc: ensure vmap_block is initialised before adding to queue Commit 8c61291fd850 (&amp;#34;mm: fix incorrect vbq reference in purge_fragmented_block&amp;#34;) extended the &amp;#39;vmap_block&amp;#39; structure to contain a &amp;#39;cpu&amp;#39; field which is set at allocation time to the id of the initialising CPU. When a new &amp;#39;vmap_block&amp;#39; is being instantiated by new_vmap_block(), the partially initialised structure is added to the local &amp;#39;vmap_block_queue&amp;#39; xarray before the &amp;#39;cpu&amp;#39; field has been initialised.  If another CPU is concurrently walking the xarray (e.g.  via vm_unmap_aliases()), then it may perform an out-of-bounds access to the remote queue thanks to an uninitialised index. This has been observed as UBSAN errors in Android:  | Internal error: UBSAN: array index out of bounds: 00000000f2005512 [#1] PREEMPT SMP  |  | Call trace:  |  purge_fragmented_block+0x204/0x21c  |  _vm_unmap_aliases+0x170/0x378  |  vm_unmap_aliases+0x1c/0x28  |  change_memory_common+0x1dc/0x26c  |  set_memory_ro+0x18/0x24  |  module_enable_ro+0x98/0x238  |  do_init_module+0x1b0/0x310 Move the initialisation of &amp;#39;vb-&amp;gt;cpu&amp;#39; in new_vmap_block() ahead of the addition to the xarray.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-46847</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-3050 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3050</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und andere nicht spezifizierte Auswirkungen zu verursachen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und andere nicht spezifizierte Auswirkungen zu verursachen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3050</guid>
    </item>
  </channel>
</rss>
