<?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 14:20:54 +0000</lastBuildDate>
    <item>
      <title>certfr-2025-avi-0252 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0252</link>
      <description>certfr-2025-avi-0252</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0252</guid>
    </item>
    <item>
      <title>EUVD-2026-344534</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-344534</link>
      <description>EUVD-2026-344534</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-344534</guid>
    </item>
    <item>
      <title>fkie_cve-2021-47638</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-47638</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ubifs: rename_whiteout: Fix double free for whiteout_ui-&amp;gt;data&lt;/p&gt;
&lt;p&gt;&amp;#39;whiteout_ui-&amp;gt;data&amp;#39; will be freed twice if space budget fail for
rename whiteout operation as following process:&lt;/p&gt;
&lt;p&gt;rename_whiteout
  dev = kmalloc
  whiteout_ui-&amp;gt;data = dev
  kfree(whiteout_ui-&amp;gt;data)  // Free first time
  iput(whiteout)
    ubifs_free_inode
      kfree(ui-&amp;gt;data)	    // Double free!&lt;/p&gt;
&lt;p&gt;KASAN reports:
==================================================================
BUG: KASAN: double-free or invalid-free in ubifs_free_inode+0x4f/0x70
Call Trace:
  kfree+0x117/0x490
  ubifs_free_inode+0x4f/0x70 [ubifs]
  i_callback+0x30/0x60
  rcu_do_batch+0x366/0xac0
  __do_softirq+0x133/0x57f&lt;/p&gt;
&lt;p&gt;Allocated by task 1506:
  kmem_cache_alloc_trace+0x3c2/0x7a0
  do_rename+0x9b7/0x1150 [ubifs]
  ubifs_rename+0x106/0x1f0 [ubifs]
  do_syscall_64+0x35/0x80&lt;/p&gt;
&lt;p&gt;Freed by task 1506:
  kfree+0x117/0x490
  do_rename.cold+0x53/0x8a [ubifs]
  ubifs_rename+0x106/0x1f0 [ubifs]
  do_syscall_64+0x35/0x80&lt;/p&gt;
&lt;p&gt;The buggy address belongs to the object at ffff88810238bed8 which
belongs to the cache kmalloc-8 of size 8
==================================================================&lt;/p&gt;
&lt;p&gt;Let ubifs_free_inode() free &amp;#39;whiteout_ui-&amp;gt;data&amp;#39;. BTW, delete unused
assignment &amp;#39;whiteout_ui-&amp;gt;data_len = 0&amp;#39;, process &amp;#39;ubifs_evict_inode()
-&amp;gt; ubifs_jnl_delete_inode() -&amp;gt; ubifs_jnl_write_inode()&amp;#39; doesn&amp;#39;t need it
(because &amp;#39;inc_nlink(whiteout)&amp;#39; won&amp;#39;t be excuted by &amp;#39;goto out_release&amp;#39;,
 and the nlink of wh…&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;ubifs: rename_whiteout: Fix double free for whiteout_ui-&amp;gt;data&lt;/p&gt;
&lt;p&gt;&amp;#39;whiteout_ui-&amp;gt;data&amp;#39; will be freed twice if space budget fail for
rename whiteout operation as following process:&lt;/p&gt;
&lt;p&gt;rename_whiteout
  dev = kmalloc
  whiteout_ui-&amp;gt;data = dev
  kfree(whiteout_ui-&amp;gt;data)  // Free first time
  iput(whiteout)
    ubifs_free_inode
      kfree(ui-&amp;gt;data)	    // Double free!&lt;/p&gt;
&lt;p&gt;KASAN reports:
==================================================================
BUG: KASAN: double-free or invalid-free in ubifs_free_inode+0x4f/0x70
Call Trace:
  kfree+0x117/0x490
  ubifs_free_inode+0x4f/0x70 [ubifs]
  i_callback+0x30/0x60
  rcu_do_batch+0x366/0xac0
  __do_softirq+0x133/0x57f&lt;/p&gt;
&lt;p&gt;Allocated by task 1506:
  kmem_cache_alloc_trace+0x3c2/0x7a0
  do_rename+0x9b7/0x1150 [ubifs]
  ubifs_rename+0x106/0x1f0 [ubifs]
  do_syscall_64+0x35/0x80&lt;/p&gt;
&lt;p&gt;Freed by task 1506:
  kfree+0x117/0x490
  do_rename.cold+0x53/0x8a [ubifs]
  ubifs_rename+0x106/0x1f0 [ubifs]
  do_syscall_64+0x35/0x80&lt;/p&gt;
&lt;p&gt;The buggy address belongs to the object at ffff88810238bed8 which
belongs to the cache kmalloc-8 of size 8
==================================================================&lt;/p&gt;
&lt;p&gt;Let ubifs_free_inode() free &amp;#39;whiteout_ui-&amp;gt;data&amp;#39;. BTW, delete unused
assignment &amp;#39;whiteout_ui-&amp;gt;data_len = 0&amp;#39;, process &amp;#39;ubifs_evict_inode()
-&amp;gt; ubifs_jnl_delete_inode() -&amp;gt; ubifs_jnl_write_inode()&amp;#39; doesn&amp;#39;t need it
(because &amp;#39;inc_nlink(whiteout)&amp;#39; won&amp;#39;t be excuted by &amp;#39;goto out_release&amp;#39;,
 and the nlink of wh…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-47638</guid>
    </item>
    <item>
      <title>GHSA-qm9f-hj62-fcm2</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-qm9f-hj62-fcm2</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ubifs: rename_whiteout: Fix double free for whiteout_ui-&amp;gt;data&lt;/p&gt;
&lt;p&gt;&amp;#39;whiteout_ui-&amp;gt;data&amp;#39; will be freed twice if space budget fail for
rename whiteout operation as following process:&lt;/p&gt;
&lt;p&gt;rename_whiteout
  dev = kmalloc
  whiteout_ui-&amp;gt;data = dev
  kfree(whiteout_ui-&amp;gt;data)  // Free first time
  iput(whiteout)
    ubifs_free_inode
      kfree(ui-&amp;gt;data)	    // Double free!&lt;/p&gt;
&lt;p&gt;KASAN reports:
==================================================================
BUG: KASAN: double-free or invalid-free in ubifs_free_inode+0x4f/0x70
Call Trace:
  kfree+0x117/0x490
  ubifs_free_inode+0x4f/0x70 [ubifs]
  i_callback+0x30/0x60
  rcu_do_batch+0x366/0xac0
  __do_softirq+0x133/0x57f&lt;/p&gt;
&lt;p&gt;Allocated by task 1506:
  kmem_cache_alloc_trace+0x3c2/0x7a0
  do_rename+0x9b7/0x1150 [ubifs]
  ubifs_rename+0x106/0x1f0 [ubifs]
  do_syscall_64+0x35/0x80&lt;/p&gt;
&lt;p&gt;Freed by task 1506:
  kfree+0x117/0x490
  do_rename.cold+0x53/0x8a [ubifs]
  ubifs_rename+0x106/0x1f0 [ubifs]
  do_syscall_64+0x35/0x80&lt;/p&gt;
&lt;p&gt;The buggy address belongs to the object at ffff88810238bed8 which
belongs to the cache kmalloc-8 of size 8
==================================================================&lt;/p&gt;
&lt;p&gt;Let ubifs_free_inode() free &amp;#39;whiteout_ui-&amp;gt;data&amp;#39;. BTW, delete unused
assignment &amp;#39;whiteout_ui-&amp;gt;data_len = 0&amp;#39;, process &amp;#39;ubifs_evict_inode()
-&amp;gt; ubifs_jnl_delete_inode() -&amp;gt; ubifs_jnl_write_inode()&amp;#39; doesn&amp;#39;t need it
(because &amp;#39;inc_nlink(whiteout)&amp;#39; won&amp;#39;t be excuted by &amp;#39;goto out_release&amp;#39;,
 and the nlink of wh…&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;ubifs: rename_whiteout: Fix double free for whiteout_ui-&amp;gt;data&lt;/p&gt;
&lt;p&gt;&amp;#39;whiteout_ui-&amp;gt;data&amp;#39; will be freed twice if space budget fail for
rename whiteout operation as following process:&lt;/p&gt;
&lt;p&gt;rename_whiteout
  dev = kmalloc
  whiteout_ui-&amp;gt;data = dev
  kfree(whiteout_ui-&amp;gt;data)  // Free first time
  iput(whiteout)
    ubifs_free_inode
      kfree(ui-&amp;gt;data)	    // Double free!&lt;/p&gt;
&lt;p&gt;KASAN reports:
==================================================================
BUG: KASAN: double-free or invalid-free in ubifs_free_inode+0x4f/0x70
Call Trace:
  kfree+0x117/0x490
  ubifs_free_inode+0x4f/0x70 [ubifs]
  i_callback+0x30/0x60
  rcu_do_batch+0x366/0xac0
  __do_softirq+0x133/0x57f&lt;/p&gt;
&lt;p&gt;Allocated by task 1506:
  kmem_cache_alloc_trace+0x3c2/0x7a0
  do_rename+0x9b7/0x1150 [ubifs]
  ubifs_rename+0x106/0x1f0 [ubifs]
  do_syscall_64+0x35/0x80&lt;/p&gt;
&lt;p&gt;Freed by task 1506:
  kfree+0x117/0x490
  do_rename.cold+0x53/0x8a [ubifs]
  ubifs_rename+0x106/0x1f0 [ubifs]
  do_syscall_64+0x35/0x80&lt;/p&gt;
&lt;p&gt;The buggy address belongs to the object at ffff88810238bed8 which
belongs to the cache kmalloc-8 of size 8
==================================================================&lt;/p&gt;
&lt;p&gt;Let ubifs_free_inode() free &amp;#39;whiteout_ui-&amp;gt;data&amp;#39;. BTW, delete unused
assignment &amp;#39;whiteout_ui-&amp;gt;data_len = 0&amp;#39;, process &amp;#39;ubifs_evict_inode()
-&amp;gt; ubifs_jnl_delete_inode() -&amp;gt; ubifs_jnl_write_inode()&amp;#39; doesn&amp;#39;t need it
(because &amp;#39;inc_nlink(whiteout)&amp;#39; won&amp;#39;t be excuted by &amp;#39;goto out_release&amp;#39;,
 and the nlink of wh…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-qm9f-hj62-fcm2</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:1176-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:1176-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:1176-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2021-47638</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47638</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:Pro:16.04:LTS: linux-oracle, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux, Ubuntu:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.4 and 130 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ubifs: rename_whiteout: Fix double free for whiteout_ui-&amp;gt;data &amp;#39;whiteout_ui-&amp;gt;data&amp;#39; will be freed twice if space budget fail for rename whiteout operation as following process: rename_whiteout   dev = kmalloc   whiteout_ui-&amp;gt;data = dev   kfree(whiteout_ui-&amp;gt;data)  // Free first time   iput(whiteout)     ubifs_free_inode       kfree(ui-&amp;gt;data)	    // Double free! KASAN reports: ================================================================== BUG: KASAN: double-free or invalid-free in ubifs_free_inode+0x4f/0x70 Call Trace:   kfree+0x117/0x490   ubifs_free_inode+0x4f/0x70 [ubifs]   i_callback+0x30/0x60   rcu_do_batch+0x366/0xac0   __do_softirq+0x133/0x57f Allocated by task 1506:   kmem_cache_alloc_trace+0x3c2/0x7a0   do_rename+0x9b7/0x1150 [ubifs]   ubifs_rename+0x106/0x1f0 [ubifs]   do_syscall_64+0x35/0x80 Freed by task 1506:   kfree+0x117/0x490   do_rename.cold+0x53/0x8a [ubifs]   ubifs_rename+0x106/0x1f0 [ubifs]   do_syscall_64+0x35/0x80 The buggy address belongs to the object at ffff88810238bed8 which belongs to the cache kmalloc-8 of size 8 ================================================================== Let ubifs_free_inode() free &amp;#39;whiteout_ui-&amp;gt;data&amp;#39;. BTW, delete unused assignment &amp;#39;whiteout_ui-&amp;gt;data_len = 0&amp;#39;, process &amp;#39;ubifs_evict_inode() -&amp;gt; ubifs_jnl_delete_inode() -&amp;gt; ubifs_jnl_write_inode()&amp;#39; doesn&amp;#39;t need it (because &amp;#39;inc_nlink(whiteout)&amp;#39; won&amp;#39;t be excuted by &amp;#39;goto out_release&amp;#39;,  and the nlink of whiteout i…&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:Pro:16.04:LTS: linux-oracle, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux, Ubuntu:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.4 and 130 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ubifs: rename_whiteout: Fix double free for whiteout_ui-&amp;gt;data &amp;#39;whiteout_ui-&amp;gt;data&amp;#39; will be freed twice if space budget fail for rename whiteout operation as following process: rename_whiteout   dev = kmalloc   whiteout_ui-&amp;gt;data = dev   kfree(whiteout_ui-&amp;gt;data)  // Free first time   iput(whiteout)     ubifs_free_inode       kfree(ui-&amp;gt;data)	    // Double free! KASAN reports: ================================================================== BUG: KASAN: double-free or invalid-free in ubifs_free_inode+0x4f/0x70 Call Trace:   kfree+0x117/0x490   ubifs_free_inode+0x4f/0x70 [ubifs]   i_callback+0x30/0x60   rcu_do_batch+0x366/0xac0   __do_softirq+0x133/0x57f Allocated by task 1506:   kmem_cache_alloc_trace+0x3c2/0x7a0   do_rename+0x9b7/0x1150 [ubifs]   ubifs_rename+0x106/0x1f0 [ubifs]   do_syscall_64+0x35/0x80 Freed by task 1506:   kfree+0x117/0x490   do_rename.cold+0x53/0x8a [ubifs]   ubifs_rename+0x106/0x1f0 [ubifs]   do_syscall_64+0x35/0x80 The buggy address belongs to the object at ffff88810238bed8 which belongs to the cache kmalloc-8 of size 8 ================================================================== Let ubifs_free_inode() free &amp;#39;whiteout_ui-&amp;gt;data&amp;#39;. BTW, delete unused assignment &amp;#39;whiteout_ui-&amp;gt;data_len = 0&amp;#39;, process &amp;#39;ubifs_evict_inode() -&amp;gt; ubifs_jnl_delete_inode() -&amp;gt; ubifs_jnl_write_inode()&amp;#39; doesn&amp;#39;t need it (because &amp;#39;inc_nlink(whiteout)&amp;#39; won&amp;#39;t be excuted by &amp;#39;goto out_release&amp;#39;,  and the nlink of whiteout i…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47638</guid>
    </item>
  </channel>
</rss>
