<?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 15:37:20 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-09290</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-09290</link>
      <description>bdu:2026-09290</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-09290</guid>
    </item>
    <item>
      <title>EUVD-2026-344879</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-344879</link>
      <description>EUVD-2026-344879</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-344879</guid>
    </item>
    <item>
      <title>fkie_cve-2022-50270</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-50270</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;f2fs: fix the assign logic of iocb&lt;/p&gt;
&lt;p&gt;commit 18ae8d12991b (&amp;#34;f2fs: show more DIO information in tracepoint&amp;#34;)
introduces iocb field in &amp;#39;f2fs_direct_IO_enter&amp;#39; trace event
And it only assigns the pointer and later it accesses its field
in trace print log.&lt;/p&gt;
&lt;p&gt;Unable to handle kernel paging request at virtual address ffffffc04cef3d30
Mem abort info:
ESR = 0x96000007
EC = 0x25: DABT (current EL), IL = 32 bits&lt;/p&gt;
&lt;p&gt;pc : trace_raw_output_f2fs_direct_IO_enter+0x54/0xa4
 lr : trace_raw_output_f2fs_direct_IO_enter+0x2c/0xa4
 sp : ffffffc0443cbbd0
 x29: ffffffc0443cbbf0 x28: ffffff8935b120d0 x27: ffffff8935b12108
 x26: ffffff8935b120f0 x25: ffffff8935b12100 x24: ffffff8935b110c0
 x23: ffffff8935b10000 x22: ffffff88859a936c x21: ffffff88859a936c
 x20: ffffff8935b110c0 x19: ffffff8935b10000 x18: ffffffc03b195060
 x17: ffffff8935b11e76 x16: 00000000000000cc x15: ffffffef855c4f2c
 x14: 0000000000000001 x13: 000000000000004e x12: ffff0000ffffff00
 x11: ffffffef86c350d0 x10: 00000000000010c0 x9 : 000000000fe0002c
 x8 : ffffffc04cef3d28 x7 : 7f7f7f7f7f7f7f7f x6 : 0000000002000000
 x5 : ffffff8935b11e9a x4 : 0000000000006250 x3 : ffff0a00ffffff04
 x2 : 0000000000000002 x1 : ffffffef86a0a31f x0 : ffffff8935b10000
 Call trace:
  trace_raw_output_f2fs_direct_IO_enter+0x54/0xa4
  print_trace_fmt+0x9c/0x138
  print_trace_line+0x154/0x254
  tracing_read_pipe+0x21c/0x380
  vfs_read+0x108/0x3ac
  ksys_read+0x7c/0xec
  __arm64_sys_read+0x20/0x…&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;f2fs: fix the assign logic of iocb&lt;/p&gt;
&lt;p&gt;commit 18ae8d12991b (&amp;#34;f2fs: show more DIO information in tracepoint&amp;#34;)
introduces iocb field in &amp;#39;f2fs_direct_IO_enter&amp;#39; trace event
And it only assigns the pointer and later it accesses its field
in trace print log.&lt;/p&gt;
&lt;p&gt;Unable to handle kernel paging request at virtual address ffffffc04cef3d30
Mem abort info:
ESR = 0x96000007
EC = 0x25: DABT (current EL), IL = 32 bits&lt;/p&gt;
&lt;p&gt;pc : trace_raw_output_f2fs_direct_IO_enter+0x54/0xa4
 lr : trace_raw_output_f2fs_direct_IO_enter+0x2c/0xa4
 sp : ffffffc0443cbbd0
 x29: ffffffc0443cbbf0 x28: ffffff8935b120d0 x27: ffffff8935b12108
 x26: ffffff8935b120f0 x25: ffffff8935b12100 x24: ffffff8935b110c0
 x23: ffffff8935b10000 x22: ffffff88859a936c x21: ffffff88859a936c
 x20: ffffff8935b110c0 x19: ffffff8935b10000 x18: ffffffc03b195060
 x17: ffffff8935b11e76 x16: 00000000000000cc x15: ffffffef855c4f2c
 x14: 0000000000000001 x13: 000000000000004e x12: ffff0000ffffff00
 x11: ffffffef86c350d0 x10: 00000000000010c0 x9 : 000000000fe0002c
 x8 : ffffffc04cef3d28 x7 : 7f7f7f7f7f7f7f7f x6 : 0000000002000000
 x5 : ffffff8935b11e9a x4 : 0000000000006250 x3 : ffff0a00ffffff04
 x2 : 0000000000000002 x1 : ffffffef86a0a31f x0 : ffffff8935b10000
 Call trace:
  trace_raw_output_f2fs_direct_IO_enter+0x54/0xa4
  print_trace_fmt+0x9c/0x138
  print_trace_line+0x154/0x254
  tracing_read_pipe+0x21c/0x380
  vfs_read+0x108/0x3ac
  ksys_read+0x7c/0xec
  __arm64_sys_read+0x20/0x…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-50270</guid>
    </item>
    <item>
      <title>GHSA-r3c5-gg5h-vgc4</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-r3c5-gg5h-vgc4</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;f2fs: fix the assign logic of iocb&lt;/p&gt;
&lt;p&gt;commit 18ae8d12991b (&amp;#34;f2fs: show more DIO information in tracepoint&amp;#34;)
introduces iocb field in &amp;#39;f2fs_direct_IO_enter&amp;#39; trace event
And it only assigns the pointer and later it accesses its field
in trace print log.&lt;/p&gt;
&lt;p&gt;Unable to handle kernel paging request at virtual address ffffffc04cef3d30
Mem abort info:
ESR = 0x96000007
EC = 0x25: DABT (current EL), IL = 32 bits&lt;/p&gt;
&lt;p&gt;pc : trace_raw_output_f2fs_direct_IO_enter+0x54/0xa4
 lr : trace_raw_output_f2fs_direct_IO_enter+0x2c/0xa4
 sp : ffffffc0443cbbd0
 x29: ffffffc0443cbbf0 x28: ffffff8935b120d0 x27: ffffff8935b12108
 x26: ffffff8935b120f0 x25: ffffff8935b12100 x24: ffffff8935b110c0
 x23: ffffff8935b10000 x22: ffffff88859a936c x21: ffffff88859a936c
 x20: ffffff8935b110c0 x19: ffffff8935b10000 x18: ffffffc03b195060
 x17: ffffff8935b11e76 x16: 00000000000000cc x15: ffffffef855c4f2c
 x14: 0000000000000001 x13: 000000000000004e x12: ffff0000ffffff00
 x11: ffffffef86c350d0 x10: 00000000000010c0 x9 : 000000000fe0002c
 x8 : ffffffc04cef3d28 x7 : 7f7f7f7f7f7f7f7f x6 : 0000000002000000
 x5 : ffffff8935b11e9a x4 : 0000000000006250 x3 : ffff0a00ffffff04
 x2 : 0000000000000002 x1 : ffffffef86a0a31f x0 : ffffff8935b10000
 Call trace:
  trace_raw_output_f2fs_direct_IO_enter+0x54/0xa4
  print_trace_fmt+0x9c/0x138
  print_trace_line+0x154/0x254
  tracing_read_pipe+0x21c/0x380
  vfs_read+0x108/0x3ac
  ksys_read+0x7c/0xec
  __arm64_sys_read+0x20/0x…&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;f2fs: fix the assign logic of iocb&lt;/p&gt;
&lt;p&gt;commit 18ae8d12991b (&amp;#34;f2fs: show more DIO information in tracepoint&amp;#34;)
introduces iocb field in &amp;#39;f2fs_direct_IO_enter&amp;#39; trace event
And it only assigns the pointer and later it accesses its field
in trace print log.&lt;/p&gt;
&lt;p&gt;Unable to handle kernel paging request at virtual address ffffffc04cef3d30
Mem abort info:
ESR = 0x96000007
EC = 0x25: DABT (current EL), IL = 32 bits&lt;/p&gt;
&lt;p&gt;pc : trace_raw_output_f2fs_direct_IO_enter+0x54/0xa4
 lr : trace_raw_output_f2fs_direct_IO_enter+0x2c/0xa4
 sp : ffffffc0443cbbd0
 x29: ffffffc0443cbbf0 x28: ffffff8935b120d0 x27: ffffff8935b12108
 x26: ffffff8935b120f0 x25: ffffff8935b12100 x24: ffffff8935b110c0
 x23: ffffff8935b10000 x22: ffffff88859a936c x21: ffffff88859a936c
 x20: ffffff8935b110c0 x19: ffffff8935b10000 x18: ffffffc03b195060
 x17: ffffff8935b11e76 x16: 00000000000000cc x15: ffffffef855c4f2c
 x14: 0000000000000001 x13: 000000000000004e x12: ffff0000ffffff00
 x11: ffffffef86c350d0 x10: 00000000000010c0 x9 : 000000000fe0002c
 x8 : ffffffc04cef3d28 x7 : 7f7f7f7f7f7f7f7f x6 : 0000000002000000
 x5 : ffffff8935b11e9a x4 : 0000000000006250 x3 : ffff0a00ffffff04
 x2 : 0000000000000002 x1 : ffffffef86a0a31f x0 : ffffff8935b10000
 Call trace:
  trace_raw_output_f2fs_direct_IO_enter+0x54/0xa4
  print_trace_fmt+0x9c/0x138
  print_trace_line+0x154/0x254
  tracing_read_pipe+0x21c/0x380
  vfs_read+0x108/0x3ac
  ksys_read+0x7c/0xec
  __arm64_sys_read+0x20/0x…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-r3c5-gg5h-vgc4</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-50270</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50270</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 78 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: f2fs: fix the assign logic of iocb commit 18ae8d12991b (&amp;#34;f2fs: show more DIO information in tracepoint&amp;#34;) introduces iocb field in &amp;#39;f2fs_direct_IO_enter&amp;#39; trace event And it only assigns the pointer and later it accesses its field in trace print log. Unable to handle kernel paging request at virtual address ffffffc04cef3d30 Mem abort info: ESR = 0x96000007 EC = 0x25: DABT (current EL), IL = 32 bits  pc : trace_raw_output_f2fs_direct_IO_enter+0x54/0xa4  lr : trace_raw_output_f2fs_direct_IO_enter+0x2c/0xa4  sp : ffffffc0443cbbd0  x29: ffffffc0443cbbf0 x28: ffffff8935b120d0 x27: ffffff8935b12108  x26: ffffff8935b120f0 x25: ffffff8935b12100 x24: ffffff8935b110c0  x23: ffffff8935b10000 x22: ffffff88859a936c x21: ffffff88859a936c  x20: ffffff8935b110c0 x19: ffffff8935b10000 x18: ffffffc03b195060  x17: ffffff8935b11e76 x16: 00000000000000cc x15: ffffffef855c4f2c  x14: 0000000000000001 x13: 000000000000004e x12: ffff0000ffffff00  x11: ffffffef86c350d0 x10: 00000000000010c0 x9 : 000000000fe0002c  x8 : ffffffc04cef3d28 x7 : 7f7f7f7f7f7f7f7f x6 : 0000000002000000  x5 : ffffff8935b11e9a x4 : 0000000000006250 x3 : ffff0a00ffffff04  x2 : 0000000000000002 x1 : ffffffef86a0a31f x0 : ffffff8935b10000  Call trace:   trace_raw_output_f2fs_direct_IO_enter+0x54/0xa4   print_trace_fmt+0x9c/0x138   print_trace_line+0x154/0x254   tracing_read_pipe+0x21c/0x380   vfs_read+0x108/0x3ac   ksys_read+0x7c/0xec   __arm64_sys_read+0x20/0x30…&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 78 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: f2fs: fix the assign logic of iocb commit 18ae8d12991b (&amp;#34;f2fs: show more DIO information in tracepoint&amp;#34;) introduces iocb field in &amp;#39;f2fs_direct_IO_enter&amp;#39; trace event And it only assigns the pointer and later it accesses its field in trace print log. Unable to handle kernel paging request at virtual address ffffffc04cef3d30 Mem abort info: ESR = 0x96000007 EC = 0x25: DABT (current EL), IL = 32 bits  pc : trace_raw_output_f2fs_direct_IO_enter+0x54/0xa4  lr : trace_raw_output_f2fs_direct_IO_enter+0x2c/0xa4  sp : ffffffc0443cbbd0  x29: ffffffc0443cbbf0 x28: ffffff8935b120d0 x27: ffffff8935b12108  x26: ffffff8935b120f0 x25: ffffff8935b12100 x24: ffffff8935b110c0  x23: ffffff8935b10000 x22: ffffff88859a936c x21: ffffff88859a936c  x20: ffffff8935b110c0 x19: ffffff8935b10000 x18: ffffffc03b195060  x17: ffffff8935b11e76 x16: 00000000000000cc x15: ffffffef855c4f2c  x14: 0000000000000001 x13: 000000000000004e x12: ffff0000ffffff00  x11: ffffffef86c350d0 x10: 00000000000010c0 x9 : 000000000fe0002c  x8 : ffffffc04cef3d28 x7 : 7f7f7f7f7f7f7f7f x6 : 0000000002000000  x5 : ffffff8935b11e9a x4 : 0000000000006250 x3 : ffff0a00ffffff04  x2 : 0000000000000002 x1 : ffffffef86a0a31f x0 : ffffff8935b10000  Call trace:   trace_raw_output_f2fs_direct_IO_enter+0x54/0xa4   print_trace_fmt+0x9c/0x138   print_trace_line+0x154/0x254   tracing_read_pipe+0x21c/0x380   vfs_read+0x108/0x3ac   ksys_read+0x7c/0xec   __arm64_sys_read+0x20/0x30…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50270</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2053 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2053</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 beschriebene 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 beschriebene Auswirkungen zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2053</guid>
    </item>
  </channel>
</rss>
