<?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 02:21:29 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-07404</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-07404</link>
      <description>bdu:2024-07404</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-07404</guid>
    </item>
    <item>
      <title>EUVD-2026-344576</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-344576</link>
      <description>EUVD-2026-344576</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-344576</guid>
    </item>
    <item>
      <title>fkie_cve-2022-48762</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-48762</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;arm64: extable: fix load_unaligned_zeropad() reg indices&lt;/p&gt;
&lt;p&gt;In ex_handler_load_unaligned_zeropad() we erroneously extract the data and
addr register indices from ex-&amp;gt;type rather than ex-&amp;gt;data. As ex-&amp;gt;type will
contain EX_TYPE_LOAD_UNALIGNED_ZEROPAD (i.e. 4):
 * We&amp;#39;ll always treat X0 as the address register, since EX_DATA_REG_ADDR is
   extracted from bits [9:5]. Thus, we may attempt to dereference an
   arbitrary address as X0 may hold an arbitrary value.
 * We&amp;#39;ll always treat X4 as the data register, since EX_DATA_REG_DATA is
   extracted from bits [4:0]. Thus we will corrupt X4 and cause arbitrary
   behaviour within load_unaligned_zeropad() and its caller.&lt;/p&gt;
&lt;p&gt;Fix this by extracting both values from ex-&amp;gt;data as originally intended.&lt;/p&gt;
&lt;p&gt;On an MTE-enabled QEMU image we are hitting the following crash:
 Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000
 Call trace:
  fixup_exception+0xc4/0x108
  __do_kernel_fault+0x3c/0x268
  do_tag_check_fault+0x3c/0x104
  do_mem_abort+0x44/0xf4
  el1_abort+0x40/0x64
  el1h_64_sync_handler+0x60/0xa0
  el1h_64_sync+0x7c/0x80
  link_path_walk+0x150/0x344
  path_openat+0xa0/0x7dc
  do_filp_open+0xb8/0x168
  do_sys_openat2+0x88/0x17c
  __arm64_sys_openat+0x74/0xa0
  invoke_syscall+0x48/0x148
  el0_svc_common+0xb8/0xf8
  do_el0_svc+0x28/0x88
  el0_svc+0x24/0x84
  el0t_64_sync_handler+0x88/0xec
  el0t_64_sync+0x1b4/0x1b8
 Code: f8695a69 71007d1f 540000…&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;arm64: extable: fix load_unaligned_zeropad() reg indices&lt;/p&gt;
&lt;p&gt;In ex_handler_load_unaligned_zeropad() we erroneously extract the data and
addr register indices from ex-&amp;gt;type rather than ex-&amp;gt;data. As ex-&amp;gt;type will
contain EX_TYPE_LOAD_UNALIGNED_ZEROPAD (i.e. 4):
 * We&amp;#39;ll always treat X0 as the address register, since EX_DATA_REG_ADDR is
   extracted from bits [9:5]. Thus, we may attempt to dereference an
   arbitrary address as X0 may hold an arbitrary value.
 * We&amp;#39;ll always treat X4 as the data register, since EX_DATA_REG_DATA is
   extracted from bits [4:0]. Thus we will corrupt X4 and cause arbitrary
   behaviour within load_unaligned_zeropad() and its caller.&lt;/p&gt;
&lt;p&gt;Fix this by extracting both values from ex-&amp;gt;data as originally intended.&lt;/p&gt;
&lt;p&gt;On an MTE-enabled QEMU image we are hitting the following crash:
 Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000
 Call trace:
  fixup_exception+0xc4/0x108
  __do_kernel_fault+0x3c/0x268
  do_tag_check_fault+0x3c/0x104
  do_mem_abort+0x44/0xf4
  el1_abort+0x40/0x64
  el1h_64_sync_handler+0x60/0xa0
  el1h_64_sync+0x7c/0x80
  link_path_walk+0x150/0x344
  path_openat+0xa0/0x7dc
  do_filp_open+0xb8/0x168
  do_sys_openat2+0x88/0x17c
  __arm64_sys_openat+0x74/0xa0
  invoke_syscall+0x48/0x148
  el0_svc_common+0xb8/0xf8
  do_el0_svc+0x28/0x88
  el0_svc+0x24/0x84
  el0t_64_sync_handler+0x88/0xec
  el0t_64_sync+0x1b4/0x1b8
 Code: f8695a69 71007d1f 540000…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-48762</guid>
    </item>
    <item>
      <title>GHSA-vj7w-cq55-7h2m</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-vj7w-cq55-7h2m</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;arm64: extable: fix load_unaligned_zeropad() reg indices&lt;/p&gt;
&lt;p&gt;In ex_handler_load_unaligned_zeropad() we erroneously extract the data and
addr register indices from ex-&amp;gt;type rather than ex-&amp;gt;data. As ex-&amp;gt;type will
contain EX_TYPE_LOAD_UNALIGNED_ZEROPAD (i.e. 4):
 * We&amp;#39;ll always treat X0 as the address register, since EX_DATA_REG_ADDR is
   extracted from bits [9:5]. Thus, we may attempt to dereference an
   arbitrary address as X0 may hold an arbitrary value.
 * We&amp;#39;ll always treat X4 as the data register, since EX_DATA_REG_DATA is
   extracted from bits [4:0]. Thus we will corrupt X4 and cause arbitrary
   behaviour within load_unaligned_zeropad() and its caller.&lt;/p&gt;
&lt;p&gt;Fix this by extracting both values from ex-&amp;gt;data as originally intended.&lt;/p&gt;
&lt;p&gt;On an MTE-enabled QEMU image we are hitting the following crash:
 Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000
 Call trace:
  fixup_exception+0xc4/0x108
  __do_kernel_fault+0x3c/0x268
  do_tag_check_fault+0x3c/0x104
  do_mem_abort+0x44/0xf4
  el1_abort+0x40/0x64
  el1h_64_sync_handler+0x60/0xa0
  el1h_64_sync+0x7c/0x80
  link_path_walk+0x150/0x344
  path_openat+0xa0/0x7dc
  do_filp_open+0xb8/0x168
  do_sys_openat2+0x88/0x17c
  __arm64_sys_openat+0x74/0xa0
  invoke_syscall+0x48/0x148
  el0_svc_common+0xb8/0xf8
  do_el0_svc+0x28/0x88
  el0_svc+0x24/0x84
  el0t_64_sync_handler+0x88/0xec
  el0t_64_sync+0x1b4/0x1b8
 Code: f8695a69 71007d1f 540000…&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;arm64: extable: fix load_unaligned_zeropad() reg indices&lt;/p&gt;
&lt;p&gt;In ex_handler_load_unaligned_zeropad() we erroneously extract the data and
addr register indices from ex-&amp;gt;type rather than ex-&amp;gt;data. As ex-&amp;gt;type will
contain EX_TYPE_LOAD_UNALIGNED_ZEROPAD (i.e. 4):
 * We&amp;#39;ll always treat X0 as the address register, since EX_DATA_REG_ADDR is
   extracted from bits [9:5]. Thus, we may attempt to dereference an
   arbitrary address as X0 may hold an arbitrary value.
 * We&amp;#39;ll always treat X4 as the data register, since EX_DATA_REG_DATA is
   extracted from bits [4:0]. Thus we will corrupt X4 and cause arbitrary
   behaviour within load_unaligned_zeropad() and its caller.&lt;/p&gt;
&lt;p&gt;Fix this by extracting both values from ex-&amp;gt;data as originally intended.&lt;/p&gt;
&lt;p&gt;On an MTE-enabled QEMU image we are hitting the following crash:
 Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000
 Call trace:
  fixup_exception+0xc4/0x108
  __do_kernel_fault+0x3c/0x268
  do_tag_check_fault+0x3c/0x104
  do_mem_abort+0x44/0xf4
  el1_abort+0x40/0x64
  el1h_64_sync_handler+0x60/0xa0
  el1h_64_sync+0x7c/0x80
  link_path_walk+0x150/0x344
  path_openat+0xa0/0x7dc
  do_filp_open+0xb8/0x168
  do_sys_openat2+0x88/0x17c
  __arm64_sys_openat+0x74/0xa0
  invoke_syscall+0x48/0x148
  el0_svc_common+0xb8/0xf8
  do_el0_svc+0x28/0x88
  el0_svc+0x24/0x84
  el0t_64_sync_handler+0x88/0xec
  el0t_64_sync+0x1b4/0x1b8
 Code: f8695a69 71007d1f 540000…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-vj7w-cq55-7h2m</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-48762</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-48762</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 54 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: arm64: extable: fix load_unaligned_zeropad() reg indices In ex_handler_load_unaligned_zeropad() we erroneously extract the data and addr register indices from ex-&amp;gt;type rather than ex-&amp;gt;data. As ex-&amp;gt;type will contain EX_TYPE_LOAD_UNALIGNED_ZEROPAD (i.e. 4):  * We&amp;#39;ll always treat X0 as the address register, since EX_DATA_REG_ADDR is    extracted from bits [9:5]. Thus, we may attempt to dereference an    arbitrary address as X0 may hold an arbitrary value.  * We&amp;#39;ll always treat X4 as the data register, since EX_DATA_REG_DATA is    extracted from bits [4:0]. Thus we will corrupt X4 and cause arbitrary    behaviour within load_unaligned_zeropad() and its caller. Fix this by extracting both values from ex-&amp;gt;data as originally intended. On an MTE-enabled QEMU image we are hitting the following crash:  Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000  Call trace:   fixup_exception+0xc4/0x108   __do_kernel_fault+0x3c/0x268   do_tag_check_fault+0x3c/0x104   do_mem_abort+0x44/0xf4   el1_abort+0x40/0x64   el1h_64_sync_handler+0x60/0xa0   el1h_64_sync+0x7c/0x80   link_path_walk+0x150/0x344   path_openat+0xa0/0x7dc   do_filp_open+0xb8/0x168   do_sys_openat2+0x88/0x17c   __arm64_sys_openat+0x74/0xa0   invoke_syscall+0x48/0x148   el0_svc_common+0xb8/0xf8   do_el0_svc+0x28/0x88   el0_svc+0x24/0x84   el0t_64_sync_handler+0x88/0xec   el0t_64_sync+0x1b4/0x1b8  Code: f8695a69 71007d1f 540000e0 9…&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 54 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: arm64: extable: fix load_unaligned_zeropad() reg indices In ex_handler_load_unaligned_zeropad() we erroneously extract the data and addr register indices from ex-&amp;gt;type rather than ex-&amp;gt;data. As ex-&amp;gt;type will contain EX_TYPE_LOAD_UNALIGNED_ZEROPAD (i.e. 4):  * We&amp;#39;ll always treat X0 as the address register, since EX_DATA_REG_ADDR is    extracted from bits [9:5]. Thus, we may attempt to dereference an    arbitrary address as X0 may hold an arbitrary value.  * We&amp;#39;ll always treat X4 as the data register, since EX_DATA_REG_DATA is    extracted from bits [4:0]. Thus we will corrupt X4 and cause arbitrary    behaviour within load_unaligned_zeropad() and its caller. Fix this by extracting both values from ex-&amp;gt;data as originally intended. On an MTE-enabled QEMU image we are hitting the following crash:  Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000  Call trace:   fixup_exception+0xc4/0x108   __do_kernel_fault+0x3c/0x268   do_tag_check_fault+0x3c/0x104   do_mem_abort+0x44/0xf4   el1_abort+0x40/0x64   el1h_64_sync_handler+0x60/0xa0   el1h_64_sync+0x7c/0x80   link_path_walk+0x150/0x344   path_openat+0xa0/0x7dc   do_filp_open+0xb8/0x168   do_sys_openat2+0x88/0x17c   __arm64_sys_openat+0x74/0xa0   invoke_syscall+0x48/0x148   el0_svc_common+0xb8/0xf8   do_el0_svc+0x28/0x88   el0_svc+0x24/0x84   el0t_64_sync_handler+0x88/0xec   el0t_64_sync+0x1b4/0x1b8  Code: f8695a69 71007d1f 540000e0 9…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-48762</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-1422 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1422</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1422</guid>
    </item>
  </channel>
</rss>
