<?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 15:15:45 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-07465</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-07465</link>
      <description>bdu:2024-07465</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-07465</guid>
    </item>
    <item>
      <title>EUVD-2026-310233</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-310233</link>
      <description>EUVD-2026-310233</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-310233</guid>
    </item>
    <item>
      <title>fkie_cve-2022-48908</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-48908</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: arcnet: com20020: Fix null-ptr-deref in com20020pci_probe()&lt;/p&gt;
&lt;p&gt;During driver initialization, the pointer of card info, i.e. the
variable &amp;#39;ci&amp;#39; is required. However, the definition of
&amp;#39;com20020pci_id_table&amp;#39; reveals that this field is empty for some
devices, which will cause null pointer dereference when initializing
these devices.&lt;/p&gt;
&lt;p&gt;The following log reveals it:&lt;/p&gt;
&lt;p&gt;[    3.973806] KASAN: null-ptr-deref in range [0x0000000000000028-0x000000000000002f]
[    3.973819] RIP: 0010:com20020pci_probe+0x18d/0x13e0 [com20020_pci]
[    3.975181] Call Trace:
[    3.976208]  local_pci_probe+0x13f/0x210
[    3.977248]  pci_device_probe+0x34c/0x6d0
[    3.977255]  ? pci_uevent+0x470/0x470
[    3.978265]  really_probe+0x24c/0x8d0
[    3.978273]  __driver_probe_device+0x1b3/0x280
[    3.979288]  driver_probe_device+0x50/0x370&lt;/p&gt;
&lt;p&gt;Fix this by checking whether the &amp;#39;ci&amp;#39; is a null pointer first.&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;net: arcnet: com20020: Fix null-ptr-deref in com20020pci_probe()&lt;/p&gt;
&lt;p&gt;During driver initialization, the pointer of card info, i.e. the
variable &amp;#39;ci&amp;#39; is required. However, the definition of
&amp;#39;com20020pci_id_table&amp;#39; reveals that this field is empty for some
devices, which will cause null pointer dereference when initializing
these devices.&lt;/p&gt;
&lt;p&gt;The following log reveals it:&lt;/p&gt;
&lt;p&gt;[    3.973806] KASAN: null-ptr-deref in range [0x0000000000000028-0x000000000000002f]
[    3.973819] RIP: 0010:com20020pci_probe+0x18d/0x13e0 [com20020_pci]
[    3.975181] Call Trace:
[    3.976208]  local_pci_probe+0x13f/0x210
[    3.977248]  pci_device_probe+0x34c/0x6d0
[    3.977255]  ? pci_uevent+0x470/0x470
[    3.978265]  really_probe+0x24c/0x8d0
[    3.978273]  __driver_probe_device+0x1b3/0x280
[    3.979288]  driver_probe_device+0x50/0x370&lt;/p&gt;
&lt;p&gt;Fix this by checking whether the &amp;#39;ci&amp;#39; is a null pointer first.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-48908</guid>
    </item>
    <item>
      <title>GHSA-cp24-c7w4-6gh4</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-cp24-c7w4-6gh4</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: arcnet: com20020: Fix null-ptr-deref in com20020pci_probe()&lt;/p&gt;
&lt;p&gt;During driver initialization, the pointer of card info, i.e. the
variable &amp;#39;ci&amp;#39; is required. However, the definition of
&amp;#39;com20020pci_id_table&amp;#39; reveals that this field is empty for some
devices, which will cause null pointer dereference when initializing
these devices.&lt;/p&gt;
&lt;p&gt;The following log reveals it:&lt;/p&gt;
&lt;p&gt;[    3.973806] KASAN: null-ptr-deref in range [0x0000000000000028-0x000000000000002f]
[    3.973819] RIP: 0010:com20020pci_probe+0x18d/0x13e0 [com20020_pci]
[    3.975181] Call Trace:
[    3.976208]  local_pci_probe+0x13f/0x210
[    3.977248]  pci_device_probe+0x34c/0x6d0
[    3.977255]  ? pci_uevent+0x470/0x470
[    3.978265]  really_probe+0x24c/0x8d0
[    3.978273]  __driver_probe_device+0x1b3/0x280
[    3.979288]  driver_probe_device+0x50/0x370&lt;/p&gt;
&lt;p&gt;Fix this by checking whether the &amp;#39;ci&amp;#39; is a null pointer first.&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;net: arcnet: com20020: Fix null-ptr-deref in com20020pci_probe()&lt;/p&gt;
&lt;p&gt;During driver initialization, the pointer of card info, i.e. the
variable &amp;#39;ci&amp;#39; is required. However, the definition of
&amp;#39;com20020pci_id_table&amp;#39; reveals that this field is empty for some
devices, which will cause null pointer dereference when initializing
these devices.&lt;/p&gt;
&lt;p&gt;The following log reveals it:&lt;/p&gt;
&lt;p&gt;[    3.973806] KASAN: null-ptr-deref in range [0x0000000000000028-0x000000000000002f]
[    3.973819] RIP: 0010:com20020pci_probe+0x18d/0x13e0 [com20020_pci]
[    3.975181] Call Trace:
[    3.976208]  local_pci_probe+0x13f/0x210
[    3.977248]  pci_device_probe+0x34c/0x6d0
[    3.977255]  ? pci_uevent+0x470/0x470
[    3.978265]  really_probe+0x24c/0x8d0
[    3.978273]  __driver_probe_device+0x1b3/0x280
[    3.979288]  driver_probe_device+0x50/0x370&lt;/p&gt;
&lt;p&gt;Fix this by checking whether the &amp;#39;ci&amp;#39; is a null pointer first.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-cp24-c7w4-6gh4</guid>
    </item>
    <item>
      <title>OESA-2024-2109 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-2109</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: 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;
f2fs: let&amp;amp;apos;s avoid panic if extent_tree is not created&#13;
&#13;
This patch avoids the below panic.&#13;
&#13;
pc : __lookup_extent_tree+0xd8/0x760
lr : f2fs_do_write_data_page+0x104/0x87c
sp : ffffffc010cbb3c0
x29: ffffffc010cbb3e0 x28: 0000000000000000
x27: ffffff8803e7f020 x26: ffffff8803e7ed40
x25: ffffff8803e7f020 x24: ffffffc010cbb460
x23: ffffffc010cbb480 x22: 0000000000000000
x21: 0000000000000000 x20: ffffffff22e90900
x19: 0000000000000000 x18: ffffffc010c5d080
x17: 0000000000000000 x16: 0000000000000020
x15: ffffffdb1acdbb88 x14: ffffff888759e2b0
x13: 0000000000000000 x12: ffffff802da49000
x11: 000000000a001200 x10: ffffff8803e7ed40
x9 : ffffff8023195800 x8 : ffffff802da49078
x7 : 0000000000000001 x6 : 0000000000000000
x5 : 0000000000000006 x4 : ffffffc010cbba28
x3 : 0000000000000000 x2 : ffffffc010cbb480
x1 : 0000000000000000 x0 : ffffff8803e7ed40
Call trace:
 __lookup_extent_tree+0xd8/0x760
 f2fs_do_write_data_page+0x104/0x87c
 f2fs_write_single_data_page+0x420/0xb60
 f2fs_write_cache_pages+0x418/0xb1c
 __f2fs_write_data_pages+0x428/0x58c
 f2fs_write_data_pages+0x30/0x40
 do_writepages+0x88/0x190
 __writeback_single_inode+0x48/0x448
 writeback_sb_inodes+0x468/0x9e8
 __writeback_inodes_wb+0xb8/0x2a4
 wb_writeback+0x33c/0x740
 wb_do_writeback+0x2b4/0x400
 wb_workfn+0xe4/0x34c
 process_one_work+0x24c/0x5bc
 worker_thread+0x3e8/0xa50…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: 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;
f2fs: let&amp;amp;apos;s avoid panic if extent_tree is not created&#13;
&#13;
This patch avoids the below panic.&#13;
&#13;
pc : __lookup_extent_tree+0xd8/0x760
lr : f2fs_do_write_data_page+0x104/0x87c
sp : ffffffc010cbb3c0
x29: ffffffc010cbb3e0 x28: 0000000000000000
x27: ffffff8803e7f020 x26: ffffff8803e7ed40
x25: ffffff8803e7f020 x24: ffffffc010cbb460
x23: ffffffc010cbb480 x22: 0000000000000000
x21: 0000000000000000 x20: ffffffff22e90900
x19: 0000000000000000 x18: ffffffc010c5d080
x17: 0000000000000000 x16: 0000000000000020
x15: ffffffdb1acdbb88 x14: ffffff888759e2b0
x13: 0000000000000000 x12: ffffff802da49000
x11: 000000000a001200 x10: ffffff8803e7ed40
x9 : ffffff8023195800 x8 : ffffff802da49078
x7 : 0000000000000001 x6 : 0000000000000000
x5 : 0000000000000006 x4 : ffffffc010cbba28
x3 : 0000000000000000 x2 : ffffffc010cbb480
x1 : 0000000000000000 x0 : ffffff8803e7ed40
Call trace:
 __lookup_extent_tree+0xd8/0x760
 f2fs_do_write_data_page+0x104/0x87c
 f2fs_write_single_data_page+0x420/0xb60
 f2fs_write_cache_pages+0x418/0xb1c
 __f2fs_write_data_pages+0x428/0x58c
 f2fs_write_data_pages+0x30/0x40
 do_writepages+0x88/0x190
 __writeback_single_inode+0x48/0x448
 writeback_sb_inodes+0x468/0x9e8
 __writeback_inodes_wb+0xb8/0x2a4
 wb_writeback+0x33c/0x740
 wb_do_writeback+0x2b4/0x400
 wb_workfn+0xe4/0x34c
 process_one_work+0x24c/0x5bc
 worker_thread+0x3e8/0xa50…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-2109</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-48908</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-48908</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, 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, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws and 119 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: arcnet: com20020: Fix null-ptr-deref in com20020pci_probe() During driver initialization, the pointer of card info, i.e. the variable &amp;#39;ci&amp;#39; is required. However, the definition of &amp;#39;com20020pci_id_table&amp;#39; reveals that this field is empty for some devices, which will cause null pointer dereference when initializing these devices. The following log reveals it: [    3.973806] KASAN: null-ptr-deref in range [0x0000000000000028-0x000000000000002f] [    3.973819] RIP: 0010:com20020pci_probe+0x18d/0x13e0 [com20020_pci] [    3.975181] Call Trace: [    3.976208]  local_pci_probe+0x13f/0x210 [    3.977248]  pci_device_probe+0x34c/0x6d0 [    3.977255]  ? pci_uevent+0x470/0x470 [    3.978265]  really_probe+0x24c/0x8d0 [    3.978273]  __driver_probe_device+0x1b3/0x280 [    3.979288]  driver_probe_device+0x50/0x370 Fix this by checking whether the &amp;#39;ci&amp;#39; is a null pointer first.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, 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, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws and 119 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: arcnet: com20020: Fix null-ptr-deref in com20020pci_probe() During driver initialization, the pointer of card info, i.e. the variable &amp;#39;ci&amp;#39; is required. However, the definition of &amp;#39;com20020pci_id_table&amp;#39; reveals that this field is empty for some devices, which will cause null pointer dereference when initializing these devices. The following log reveals it: [    3.973806] KASAN: null-ptr-deref in range [0x0000000000000028-0x000000000000002f] [    3.973819] RIP: 0010:com20020pci_probe+0x18d/0x13e0 [com20020_pci] [    3.975181] Call Trace: [    3.976208]  local_pci_probe+0x13f/0x210 [    3.977248]  pci_device_probe+0x34c/0x6d0 [    3.977255]  ? pci_uevent+0x470/0x470 [    3.978265]  really_probe+0x24c/0x8d0 [    3.978273]  __driver_probe_device+0x1b3/0x280 [    3.979288]  driver_probe_device+0x50/0x370 Fix this by checking whether the &amp;#39;ci&amp;#39; is a null pointer first.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-48908</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-1898 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1898</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder einen unspezifischen Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder einen unspezifischen Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1898</guid>
    </item>
  </channel>
</rss>
