<?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 17:14:40 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-05732</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-05732</link>
      <description>bdu:2026-05732</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-05732</guid>
    </item>
    <item>
      <title>EUVD-2026-311064</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-311064</link>
      <description>EUVD-2026-311064</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-311064</guid>
    </item>
    <item>
      <title>fkie_cve-2022-50174</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-50174</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: hinic: avoid kernel hung in hinic_get_stats64()&lt;/p&gt;
&lt;p&gt;When using hinic device as a bond slave device, and reading device stats
of master bond device, the kernel may hung.&lt;/p&gt;
&lt;p&gt;The kernel panic calltrace as follows:
Kernel panic - not syncing: softlockup: hung tasks
Call trace:
  native_queued_spin_lock_slowpath+0x1ec/0x31c
  dev_get_stats+0x60/0xcc
  dev_seq_printf_stats+0x40/0x120
  dev_seq_show+0x1c/0x40
  seq_read_iter+0x3c8/0x4dc
  seq_read+0xe0/0x130
  proc_reg_read+0xa8/0xe0
  vfs_read+0xb0/0x1d4
  ksys_read+0x70/0xfc
  __arm64_sys_read+0x20/0x30
  el0_svc_common+0x88/0x234
  do_el0_svc+0x2c/0x90
  el0_svc+0x1c/0x30
  el0_sync_handler+0xa8/0xb0
  el0_sync+0x148/0x180&lt;/p&gt;
&lt;p&gt;And the calltrace of task that actually caused kernel hungs as follows:
  __switch_to+124
  __schedule+548
  schedule+72
  schedule_timeout+348
  __down_common+188
  __down+24
  down+104
  hinic_get_stats64+44 [hinic]
  dev_get_stats+92
  bond_get_stats+172 [bonding]
  dev_get_stats+92
  dev_seq_printf_stats+60
  dev_seq_show+24
  seq_read_iter+964
  seq_read+220
  proc_reg_read+164
  vfs_read+172
  ksys_read+108
  __arm64_sys_read+28
  el0_svc_common+132
  do_el0_svc+40
  el0_svc+24
  el0_sync_handler+164
  el0_sync+324&lt;/p&gt;
&lt;p&gt;When getting device stats from bond, kernel will call bond_get_stats().
It first holds the spinlock bond-&amp;gt;stats_lock, and then call
hinic_get_stats64() to collect hinic device&amp;#39;s stats.
However, hinic_get_stats64() calls `do…&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: hinic: avoid kernel hung in hinic_get_stats64()&lt;/p&gt;
&lt;p&gt;When using hinic device as a bond slave device, and reading device stats
of master bond device, the kernel may hung.&lt;/p&gt;
&lt;p&gt;The kernel panic calltrace as follows:
Kernel panic - not syncing: softlockup: hung tasks
Call trace:
  native_queued_spin_lock_slowpath+0x1ec/0x31c
  dev_get_stats+0x60/0xcc
  dev_seq_printf_stats+0x40/0x120
  dev_seq_show+0x1c/0x40
  seq_read_iter+0x3c8/0x4dc
  seq_read+0xe0/0x130
  proc_reg_read+0xa8/0xe0
  vfs_read+0xb0/0x1d4
  ksys_read+0x70/0xfc
  __arm64_sys_read+0x20/0x30
  el0_svc_common+0x88/0x234
  do_el0_svc+0x2c/0x90
  el0_svc+0x1c/0x30
  el0_sync_handler+0xa8/0xb0
  el0_sync+0x148/0x180&lt;/p&gt;
&lt;p&gt;And the calltrace of task that actually caused kernel hungs as follows:
  __switch_to+124
  __schedule+548
  schedule+72
  schedule_timeout+348
  __down_common+188
  __down+24
  down+104
  hinic_get_stats64+44 [hinic]
  dev_get_stats+92
  bond_get_stats+172 [bonding]
  dev_get_stats+92
  dev_seq_printf_stats+60
  dev_seq_show+24
  seq_read_iter+964
  seq_read+220
  proc_reg_read+164
  vfs_read+172
  ksys_read+108
  __arm64_sys_read+28
  el0_svc_common+132
  do_el0_svc+40
  el0_svc+24
  el0_sync_handler+164
  el0_sync+324&lt;/p&gt;
&lt;p&gt;When getting device stats from bond, kernel will call bond_get_stats().
It first holds the spinlock bond-&amp;gt;stats_lock, and then call
hinic_get_stats64() to collect hinic device&amp;#39;s stats.
However, hinic_get_stats64() calls `do…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-50174</guid>
    </item>
    <item>
      <title>GHSA-w89w-9482-vj48</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-w89w-9482-vj48</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: hinic: avoid kernel hung in hinic_get_stats64()&lt;/p&gt;
&lt;p&gt;When using hinic device as a bond slave device, and reading device stats
of master bond device, the kernel may hung.&lt;/p&gt;
&lt;p&gt;The kernel panic calltrace as follows:
Kernel panic - not syncing: softlockup: hung tasks
Call trace:
  native_queued_spin_lock_slowpath+0x1ec/0x31c
  dev_get_stats+0x60/0xcc
  dev_seq_printf_stats+0x40/0x120
  dev_seq_show+0x1c/0x40
  seq_read_iter+0x3c8/0x4dc
  seq_read+0xe0/0x130
  proc_reg_read+0xa8/0xe0
  vfs_read+0xb0/0x1d4
  ksys_read+0x70/0xfc
  __arm64_sys_read+0x20/0x30
  el0_svc_common+0x88/0x234
  do_el0_svc+0x2c/0x90
  el0_svc+0x1c/0x30
  el0_sync_handler+0xa8/0xb0
  el0_sync+0x148/0x180&lt;/p&gt;
&lt;p&gt;And the calltrace of task that actually caused kernel hungs as follows:
  __switch_to+124
  __schedule+548
  schedule+72
  schedule_timeout+348
  __down_common+188
  __down+24
  down+104
  hinic_get_stats64+44 [hinic]
  dev_get_stats+92
  bond_get_stats+172 [bonding]
  dev_get_stats+92
  dev_seq_printf_stats+60
  dev_seq_show+24
  seq_read_iter+964
  seq_read+220
  proc_reg_read+164
  vfs_read+172
  ksys_read+108
  __arm64_sys_read+28
  el0_svc_common+132
  do_el0_svc+40
  el0_svc+24
  el0_sync_handler+164
  el0_sync+324&lt;/p&gt;
&lt;p&gt;When getting device stats from bond, kernel will call bond_get_stats().
It first holds the spinlock bond-&amp;gt;stats_lock, and then call
hinic_get_stats64() to collect hinic device&amp;#39;s stats.
However, hinic_get_stats64() calls `do…&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: hinic: avoid kernel hung in hinic_get_stats64()&lt;/p&gt;
&lt;p&gt;When using hinic device as a bond slave device, and reading device stats
of master bond device, the kernel may hung.&lt;/p&gt;
&lt;p&gt;The kernel panic calltrace as follows:
Kernel panic - not syncing: softlockup: hung tasks
Call trace:
  native_queued_spin_lock_slowpath+0x1ec/0x31c
  dev_get_stats+0x60/0xcc
  dev_seq_printf_stats+0x40/0x120
  dev_seq_show+0x1c/0x40
  seq_read_iter+0x3c8/0x4dc
  seq_read+0xe0/0x130
  proc_reg_read+0xa8/0xe0
  vfs_read+0xb0/0x1d4
  ksys_read+0x70/0xfc
  __arm64_sys_read+0x20/0x30
  el0_svc_common+0x88/0x234
  do_el0_svc+0x2c/0x90
  el0_svc+0x1c/0x30
  el0_sync_handler+0xa8/0xb0
  el0_sync+0x148/0x180&lt;/p&gt;
&lt;p&gt;And the calltrace of task that actually caused kernel hungs as follows:
  __switch_to+124
  __schedule+548
  schedule+72
  schedule_timeout+348
  __down_common+188
  __down+24
  down+104
  hinic_get_stats64+44 [hinic]
  dev_get_stats+92
  bond_get_stats+172 [bonding]
  dev_get_stats+92
  dev_seq_printf_stats+60
  dev_seq_show+24
  seq_read_iter+964
  seq_read+220
  proc_reg_read+164
  vfs_read+172
  ksys_read+108
  __arm64_sys_read+28
  el0_svc_common+132
  do_el0_svc+40
  el0_svc+24
  el0_sync_handler+164
  el0_sync+324&lt;/p&gt;
&lt;p&gt;When getting device stats from bond, kernel will call bond_get_stats().
It first holds the spinlock bond-&amp;gt;stats_lock, and then call
hinic_get_stats64() to collect hinic device&amp;#39;s stats.
However, hinic_get_stats64() calls `do…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-w89w-9482-vj48</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-50174</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50174</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 140 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: hinic: avoid kernel hung in hinic_get_stats64() When using hinic device as a bond slave device, and reading device stats of master bond device, the kernel may hung. The kernel panic calltrace as follows: Kernel panic - not syncing: softlockup: hung tasks Call trace:   native_queued_spin_lock_slowpath+0x1ec/0x31c   dev_get_stats+0x60/0xcc   dev_seq_printf_stats+0x40/0x120   dev_seq_show+0x1c/0x40   seq_read_iter+0x3c8/0x4dc   seq_read+0xe0/0x130   proc_reg_read+0xa8/0xe0   vfs_read+0xb0/0x1d4   ksys_read+0x70/0xfc   __arm64_sys_read+0x20/0x30   el0_svc_common+0x88/0x234   do_el0_svc+0x2c/0x90   el0_svc+0x1c/0x30   el0_sync_handler+0xa8/0xb0   el0_sync+0x148/0x180 And the calltrace of task that actually caused kernel hungs as follows:   __switch_to+124   __schedule+548   schedule+72   schedule_timeout+348   __down_common+188   __down+24   down+104   hinic_get_stats64+44 [hinic]   dev_get_stats+92   bond_get_stats+172 [bonding]   dev_get_stats+92   dev_seq_printf_stats+60   dev_seq_show+24   seq_read_iter+964   seq_read+220   proc_reg_read+164   vfs_read+172   ksys_read+108   __arm64_sys_read+28   el0_svc_common+132   do_el0_svc+40   el0_svc+24   el0_sync_handler+164   el0_sync+324 When getting device stats from bond, kernel will call bond_get_stats(). It first holds the spinlock bond-&amp;gt;stats_lock, and then call hinic_get_stats64() to collect hinic device&amp;#39;s stats. However, hinic_get_stats64() calls `down(&amp;amp;n…&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: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:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 140 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: hinic: avoid kernel hung in hinic_get_stats64() When using hinic device as a bond slave device, and reading device stats of master bond device, the kernel may hung. The kernel panic calltrace as follows: Kernel panic - not syncing: softlockup: hung tasks Call trace:   native_queued_spin_lock_slowpath+0x1ec/0x31c   dev_get_stats+0x60/0xcc   dev_seq_printf_stats+0x40/0x120   dev_seq_show+0x1c/0x40   seq_read_iter+0x3c8/0x4dc   seq_read+0xe0/0x130   proc_reg_read+0xa8/0xe0   vfs_read+0xb0/0x1d4   ksys_read+0x70/0xfc   __arm64_sys_read+0x20/0x30   el0_svc_common+0x88/0x234   do_el0_svc+0x2c/0x90   el0_svc+0x1c/0x30   el0_sync_handler+0xa8/0xb0   el0_sync+0x148/0x180 And the calltrace of task that actually caused kernel hungs as follows:   __switch_to+124   __schedule+548   schedule+72   schedule_timeout+348   __down_common+188   __down+24   down+104   hinic_get_stats64+44 [hinic]   dev_get_stats+92   bond_get_stats+172 [bonding]   dev_get_stats+92   dev_seq_printf_stats+60   dev_seq_show+24   seq_read_iter+964   seq_read+220   proc_reg_read+164   vfs_read+172   ksys_read+108   __arm64_sys_read+28   el0_svc_common+132   do_el0_svc+40   el0_svc+24   el0_sync_handler+164   el0_sync+324 When getting device stats from bond, kernel will call bond_get_stats(). It first holds the spinlock bond-&amp;gt;stats_lock, and then call hinic_get_stats64() to collect hinic device&amp;#39;s stats. However, hinic_get_stats64() calls `down(&amp;amp;n…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50174</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-1350 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1350</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.&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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1350</guid>
    </item>
  </channel>
</rss>
