<?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>Mon, 05 Oct 2026 04:21:29 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-12041</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-12041</link>
      <description>bdu:2025-12041</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-12041</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-21981</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-21981</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, 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:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2025-21981</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0333 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0333</link>
      <description>certfr-2025-avi-0333</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0333</guid>
    </item>
    <item>
      <title>EUVD-2026-314129</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-314129</link>
      <description>EUVD-2026-314129</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-314129</guid>
    </item>
    <item>
      <title>fkie_cve-2025-21981</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-21981</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ice: fix memory leak in aRFS after reset&lt;/p&gt;
&lt;p&gt;Fix aRFS (accelerated Receive Flow Steering) structures memory leak by
adding a checker to verify if aRFS memory is already allocated while
configuring VSI. aRFS objects are allocated in two cases:
- as part of VSI initialization (at probe), and
- as part of reset handling&lt;/p&gt;
&lt;p&gt;However, VSI reconfiguration executed during reset involves memory
allocation one more time, without prior releasing already allocated
resources. This led to the memory leak with the following signature:&lt;/p&gt;
&lt;p&gt;[root@os-delivery ~]# cat /sys/kernel/debug/kmemleak
unreferenced object 0xff3c1ca7252e6000 (size 8192):
  comm &amp;#34;kworker/0:0&amp;#34;, pid 8, jiffies 4296833052
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace (crc 0):
    [&amp;lt;ffffffff991ec485&amp;gt;] __kmalloc_cache_noprof+0x275/0x340
    [&amp;lt;ffffffffc0a6e06a&amp;gt;] ice_init_arfs+0x3a/0xe0 [ice]
    [&amp;lt;ffffffffc09f1027&amp;gt;] ice_vsi_cfg_def+0x607/0x850 [ice]
    [&amp;lt;ffffffffc09f244b&amp;gt;] ice_vsi_setup+0x5b/0x130 [ice]
    [&amp;lt;ffffffffc09c2131&amp;gt;] ice_init+0x1c1/0x460 [ice]
    [&amp;lt;ffffffffc09c64af&amp;gt;] ice_probe+0x2af/0x520 [ice]
    [&amp;lt;ffffffff994fbcd3&amp;gt;] local_pci_probe+0x43/0xa0
    [&amp;lt;ffffffff98f07103&amp;gt;] work_for_cpu_fn+0x13/0x20
    [&amp;lt;ffffffff98f0b6d9&amp;gt;] process_one_work+0x179/0x390
    [&amp;lt;ffffffff98f0c1e9&amp;gt;] worker_thread+0x239/0x340
    [&amp;lt;ffffffff98f14abc&amp;gt;…&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;ice: fix memory leak in aRFS after reset&lt;/p&gt;
&lt;p&gt;Fix aRFS (accelerated Receive Flow Steering) structures memory leak by
adding a checker to verify if aRFS memory is already allocated while
configuring VSI. aRFS objects are allocated in two cases:
- as part of VSI initialization (at probe), and
- as part of reset handling&lt;/p&gt;
&lt;p&gt;However, VSI reconfiguration executed during reset involves memory
allocation one more time, without prior releasing already allocated
resources. This led to the memory leak with the following signature:&lt;/p&gt;
&lt;p&gt;[root@os-delivery ~]# cat /sys/kernel/debug/kmemleak
unreferenced object 0xff3c1ca7252e6000 (size 8192):
  comm &amp;#34;kworker/0:0&amp;#34;, pid 8, jiffies 4296833052
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace (crc 0):
    [&amp;lt;ffffffff991ec485&amp;gt;] __kmalloc_cache_noprof+0x275/0x340
    [&amp;lt;ffffffffc0a6e06a&amp;gt;] ice_init_arfs+0x3a/0xe0 [ice]
    [&amp;lt;ffffffffc09f1027&amp;gt;] ice_vsi_cfg_def+0x607/0x850 [ice]
    [&amp;lt;ffffffffc09f244b&amp;gt;] ice_vsi_setup+0x5b/0x130 [ice]
    [&amp;lt;ffffffffc09c2131&amp;gt;] ice_init+0x1c1/0x460 [ice]
    [&amp;lt;ffffffffc09c64af&amp;gt;] ice_probe+0x2af/0x520 [ice]
    [&amp;lt;ffffffff994fbcd3&amp;gt;] local_pci_probe+0x43/0xa0
    [&amp;lt;ffffffff98f07103&amp;gt;] work_for_cpu_fn+0x13/0x20
    [&amp;lt;ffffffff98f0b6d9&amp;gt;] process_one_work+0x179/0x390
    [&amp;lt;ffffffff98f0c1e9&amp;gt;] worker_thread+0x239/0x340
    [&amp;lt;ffffffff98f14abc&amp;gt;…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-21981</guid>
    </item>
    <item>
      <title>GHSA-7jcj-vjq7-xp8h</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-7jcj-vjq7-xp8h</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ice: fix memory leak in aRFS after reset&lt;/p&gt;
&lt;p&gt;Fix aRFS (accelerated Receive Flow Steering) structures memory leak by
adding a checker to verify if aRFS memory is already allocated while
configuring VSI. aRFS objects are allocated in two cases:
- as part of VSI initialization (at probe), and
- as part of reset handling&lt;/p&gt;
&lt;p&gt;However, VSI reconfiguration executed during reset involves memory
allocation one more time, without prior releasing already allocated
resources. This led to the memory leak with the following signature:&lt;/p&gt;
&lt;p&gt;[root@os-delivery ~]# cat /sys/kernel/debug/kmemleak
unreferenced object 0xff3c1ca7252e6000 (size 8192):
  comm &amp;#34;kworker/0:0&amp;#34;, pid 8, jiffies 4296833052
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace (crc 0):
    [&amp;lt;ffffffff991ec485&amp;gt;] __kmalloc_cache_noprof+0x275/0x340
    [&amp;lt;ffffffffc0a6e06a&amp;gt;] ice_init_arfs+0x3a/0xe0 [ice]
    [&amp;lt;ffffffffc09f1027&amp;gt;] ice_vsi_cfg_def+0x607/0x850 [ice]
    [&amp;lt;ffffffffc09f244b&amp;gt;] ice_vsi_setup+0x5b/0x130 [ice]
    [&amp;lt;ffffffffc09c2131&amp;gt;] ice_init+0x1c1/0x460 [ice]
    [&amp;lt;ffffffffc09c64af&amp;gt;] ice_probe+0x2af/0x520 [ice]
    [&amp;lt;ffffffff994fbcd3&amp;gt;] local_pci_probe+0x43/0xa0
    [&amp;lt;ffffffff98f07103&amp;gt;] work_for_cpu_fn+0x13/0x20
    [&amp;lt;ffffffff98f0b6d9&amp;gt;] process_one_work+0x179/0x390
    [&amp;lt;ffffffff98f0c1e9&amp;gt;] worker_thread+0x239/0x340
    [&amp;lt;ffffffff98f14abc&amp;gt;…&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;ice: fix memory leak in aRFS after reset&lt;/p&gt;
&lt;p&gt;Fix aRFS (accelerated Receive Flow Steering) structures memory leak by
adding a checker to verify if aRFS memory is already allocated while
configuring VSI. aRFS objects are allocated in two cases:
- as part of VSI initialization (at probe), and
- as part of reset handling&lt;/p&gt;
&lt;p&gt;However, VSI reconfiguration executed during reset involves memory
allocation one more time, without prior releasing already allocated
resources. This led to the memory leak with the following signature:&lt;/p&gt;
&lt;p&gt;[root@os-delivery ~]# cat /sys/kernel/debug/kmemleak
unreferenced object 0xff3c1ca7252e6000 (size 8192):
  comm &amp;#34;kworker/0:0&amp;#34;, pid 8, jiffies 4296833052
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace (crc 0):
    [&amp;lt;ffffffff991ec485&amp;gt;] __kmalloc_cache_noprof+0x275/0x340
    [&amp;lt;ffffffffc0a6e06a&amp;gt;] ice_init_arfs+0x3a/0xe0 [ice]
    [&amp;lt;ffffffffc09f1027&amp;gt;] ice_vsi_cfg_def+0x607/0x850 [ice]
    [&amp;lt;ffffffffc09f244b&amp;gt;] ice_vsi_setup+0x5b/0x130 [ice]
    [&amp;lt;ffffffffc09c2131&amp;gt;] ice_init+0x1c1/0x460 [ice]
    [&amp;lt;ffffffffc09c64af&amp;gt;] ice_probe+0x2af/0x520 [ice]
    [&amp;lt;ffffffff994fbcd3&amp;gt;] local_pci_probe+0x43/0xa0
    [&amp;lt;ffffffff98f07103&amp;gt;] work_for_cpu_fn+0x13/0x20
    [&amp;lt;ffffffff98f0b6d9&amp;gt;] process_one_work+0x179/0x390
    [&amp;lt;ffffffff98f0c1e9&amp;gt;] worker_thread+0x239/0x340
    [&amp;lt;ffffffff98f14abc&amp;gt;…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-7jcj-vjq7-xp8h</guid>
    </item>
    <item>
      <title>msrc_CVE-2025-21981 — ice: fix memory leak in aRFS after reset</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2025-21981</link>
      <description>msrc_CVE-2025-21981</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2025-21981</guid>
    </item>
    <item>
      <title>OESA-2026-1341 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2026-1341</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP4: 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:kernel/resource: fix kfree() of bootmem memory againSince commit ebff7d8f270d ( mem hotunplug: fix kfree() of bootmemmemory ), we could get a resource allocated during boot viaalloc_resource().  And it s required to release the resource usingfree_resource().  Howerver, many people use kfree directly which willresult in kernel BUG.  In order to fix this without fixing every callsite, just leak a couple of bytes in such corner case.(CVE-2022-49190)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:drivers: staging: rtl8723bs: Fix deadlock in rtw_surveydone_event_callback()There is a deadlock in rtw_surveydone_event_callback(),which is shown below:   (Thread 1)                  |      (Thread 2)                               | _set_timer()rtw_surveydone_event_callback()|  mod_timer() spin_lock_bh() //(1)          |  (wait a time) ...                           | rtw_scan_timeout_handler() del_timer_sync()              |  spin_lock_bh() //(2) (wait timer to stop)          |  ...We hold pmlmepriv-&amp;amp;gt;lock in position (1) of thread 1 and usedel_timer_sync() to wait timer to stop, but timer handleralso need pmlmepriv-&amp;amp;gt;lock in position (2) of thread 2.As a result, rtw_surveydone_event_callback() will block forever.This patch extracts del_timer_sync() from the protection ofspin_lock_bh(), which could let timer handler to obta…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP4: 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:kernel/resource: fix kfree() of bootmem memory againSince commit ebff7d8f270d ( mem hotunplug: fix kfree() of bootmemmemory ), we could get a resource allocated during boot viaalloc_resource().  And it s required to release the resource usingfree_resource().  Howerver, many people use kfree directly which willresult in kernel BUG.  In order to fix this without fixing every callsite, just leak a couple of bytes in such corner case.(CVE-2022-49190)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:drivers: staging: rtl8723bs: Fix deadlock in rtw_surveydone_event_callback()There is a deadlock in rtw_surveydone_event_callback(),which is shown below:   (Thread 1)                  |      (Thread 2)                               | _set_timer()rtw_surveydone_event_callback()|  mod_timer() spin_lock_bh() //(1)          |  (wait a time) ...                           | rtw_scan_timeout_handler() del_timer_sync()              |  spin_lock_bh() //(2) (wait timer to stop)          |  ...We hold pmlmepriv-&amp;amp;gt;lock in position (1) of thread 1 and usedel_timer_sync() to wait timer to stop, but timer handleralso need pmlmepriv-&amp;amp;gt;lock in position (2) of thread 2.As a result, rtw_surveydone_event_callback() will block forever.This patch extracts del_timer_sync() from the protection ofspin_lock_bh(), which could let timer handler to obta…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2026-1341</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:01614-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:01614-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2025:01614-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-21981</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-21981</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 148 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ice: fix memory leak in aRFS after reset Fix aRFS (accelerated Receive Flow Steering) structures memory leak by adding a checker to verify if aRFS memory is already allocated while configuring VSI. aRFS objects are allocated in two cases: - as part of VSI initialization (at probe), and - as part of reset handling However, VSI reconfiguration executed during reset involves memory allocation one more time, without prior releasing already allocated resources. This led to the memory leak with the following signature: [root@os-delivery ~]# cat /sys/kernel/debug/kmemleak unreferenced object 0xff3c1ca7252e6000 (size 8192):   comm &amp;#34;kworker/0:0&amp;#34;, pid 8, jiffies 4296833052   hex dump (first 32 bytes):     00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................     00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................   backtrace (crc 0):     [&amp;lt;ffffffff991ec485&amp;gt;] __kmalloc_cache_noprof+0x275/0x340     [&amp;lt;ffffffffc0a6e06a&amp;gt;] ice_init_arfs+0x3a/0xe0 [ice]     [&amp;lt;ffffffffc09f1027&amp;gt;] ice_vsi_cfg_def+0x607/0x850 [ice]     [&amp;lt;ffffffffc09f244b&amp;gt;] ice_vsi_setup+0x5b/0x130 [ice]     [&amp;lt;ffffffffc09c2131&amp;gt;] ice_init+0x1c1/0x460 [ice]     [&amp;lt;ffffffffc09c64af&amp;gt;] ice_probe+0x2af/0x520 [ice]     [&amp;lt;ffffffff994fbcd3&amp;gt;] local_pci_probe+0x43/0xa0     [&amp;lt;ffffffff98f07103&amp;gt;] work_for_cpu_fn+0x13/0x20     [&amp;lt;ffffffff98f0b6d9&amp;gt;] process_one_work+0x179/0x390     [&amp;lt;ffffffff98f0c1e9&amp;gt;] worker_thread+0x239/0x340     [&amp;lt;ffffffff98f14abc&amp;gt;] kt…&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 148 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ice: fix memory leak in aRFS after reset Fix aRFS (accelerated Receive Flow Steering) structures memory leak by adding a checker to verify if aRFS memory is already allocated while configuring VSI. aRFS objects are allocated in two cases: - as part of VSI initialization (at probe), and - as part of reset handling However, VSI reconfiguration executed during reset involves memory allocation one more time, without prior releasing already allocated resources. This led to the memory leak with the following signature: [root@os-delivery ~]# cat /sys/kernel/debug/kmemleak unreferenced object 0xff3c1ca7252e6000 (size 8192):   comm &amp;#34;kworker/0:0&amp;#34;, pid 8, jiffies 4296833052   hex dump (first 32 bytes):     00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................     00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................   backtrace (crc 0):     [&amp;lt;ffffffff991ec485&amp;gt;] __kmalloc_cache_noprof+0x275/0x340     [&amp;lt;ffffffffc0a6e06a&amp;gt;] ice_init_arfs+0x3a/0xe0 [ice]     [&amp;lt;ffffffffc09f1027&amp;gt;] ice_vsi_cfg_def+0x607/0x850 [ice]     [&amp;lt;ffffffffc09f244b&amp;gt;] ice_vsi_setup+0x5b/0x130 [ice]     [&amp;lt;ffffffffc09c2131&amp;gt;] ice_init+0x1c1/0x460 [ice]     [&amp;lt;ffffffffc09c64af&amp;gt;] ice_probe+0x2af/0x520 [ice]     [&amp;lt;ffffffff994fbcd3&amp;gt;] local_pci_probe+0x43/0xa0     [&amp;lt;ffffffff98f07103&amp;gt;] work_for_cpu_fn+0x13/0x20     [&amp;lt;ffffffff98f0b6d9&amp;gt;] process_one_work+0x179/0x390     [&amp;lt;ffffffff98f0c1e9&amp;gt;] worker_thread+0x239/0x340     [&amp;lt;ffffffff98f14abc&amp;gt;] kt…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-21981</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-0683 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0683</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial-of-Service auszulösen und um nicht näher spezifizierte Auswirkungen zu erzielen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial-of-Service auszulösen und um nicht näher spezifizierte Auswirkungen zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0683</guid>
    </item>
  </channel>
</rss>
