<?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 08:56:16 +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-310455</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-310455</link>
      <description>EUVD-2026-310455</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-310455</guid>
    </item>
    <item>
      <title>fkie_cve-2022-49277</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-49277</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;jffs2: fix memory leak in jffs2_do_mount_fs&lt;/p&gt;
&lt;p&gt;If jffs2_build_filesystem() in jffs2_do_mount_fs() returns an error,
we can observe the following kmemleak report:&lt;/p&gt;
&lt;p&gt;--------------------------------------------
unreferenced object 0xffff88811b25a640 (size 64):
  comm &amp;#34;mount&amp;#34;, pid 691, jiffies 4294957728 (age 71.952s)
  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:
    [&amp;lt;ffffffffa493be24&amp;gt;] kmem_cache_alloc_trace+0x584/0x880
    [&amp;lt;ffffffffa5423a06&amp;gt;] jffs2_sum_init+0x86/0x130
    [&amp;lt;ffffffffa5400e58&amp;gt;] jffs2_do_mount_fs+0x798/0xac0
    [&amp;lt;ffffffffa540acf3&amp;gt;] jffs2_do_fill_super+0x383/0xc30
    [&amp;lt;ffffffffa540c00a&amp;gt;] jffs2_fill_super+0x2ea/0x4c0
    [...]
unreferenced object 0xffff88812c760000 (size 65536):
  comm &amp;#34;mount&amp;#34;, pid 691, jiffies 4294957728 (age 71.952s)
  hex dump (first 32 bytes):
    bb bb bb bb bb bb bb bb bb bb bb bb bb bb bb bb  ................
    bb bb bb bb bb bb bb bb bb bb bb bb bb bb bb bb  ................
  backtrace:
    [&amp;lt;ffffffffa493a449&amp;gt;] __kmalloc+0x6b9/0x910
    [&amp;lt;ffffffffa5423a57&amp;gt;] jffs2_sum_init+0xd7/0x130
    [&amp;lt;ffffffffa5400e58&amp;gt;] jffs2_do_mount_fs+0x798/0xac0
    [&amp;lt;ffffffffa540acf3&amp;gt;] jffs2_do_fill_super+0x383/0xc30
    [&amp;lt;ffffffffa540c00a&amp;gt;] jffs2_fill_super+0x2ea/0x4c0
    [...]
--------------------------------------------&lt;/p&gt;
&lt;p&gt;This is because the resources allo…&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;jffs2: fix memory leak in jffs2_do_mount_fs&lt;/p&gt;
&lt;p&gt;If jffs2_build_filesystem() in jffs2_do_mount_fs() returns an error,
we can observe the following kmemleak report:&lt;/p&gt;
&lt;p&gt;--------------------------------------------
unreferenced object 0xffff88811b25a640 (size 64):
  comm &amp;#34;mount&amp;#34;, pid 691, jiffies 4294957728 (age 71.952s)
  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:
    [&amp;lt;ffffffffa493be24&amp;gt;] kmem_cache_alloc_trace+0x584/0x880
    [&amp;lt;ffffffffa5423a06&amp;gt;] jffs2_sum_init+0x86/0x130
    [&amp;lt;ffffffffa5400e58&amp;gt;] jffs2_do_mount_fs+0x798/0xac0
    [&amp;lt;ffffffffa540acf3&amp;gt;] jffs2_do_fill_super+0x383/0xc30
    [&amp;lt;ffffffffa540c00a&amp;gt;] jffs2_fill_super+0x2ea/0x4c0
    [...]
unreferenced object 0xffff88812c760000 (size 65536):
  comm &amp;#34;mount&amp;#34;, pid 691, jiffies 4294957728 (age 71.952s)
  hex dump (first 32 bytes):
    bb bb bb bb bb bb bb bb bb bb bb bb bb bb bb bb  ................
    bb bb bb bb bb bb bb bb bb bb bb bb bb bb bb bb  ................
  backtrace:
    [&amp;lt;ffffffffa493a449&amp;gt;] __kmalloc+0x6b9/0x910
    [&amp;lt;ffffffffa5423a57&amp;gt;] jffs2_sum_init+0xd7/0x130
    [&amp;lt;ffffffffa5400e58&amp;gt;] jffs2_do_mount_fs+0x798/0xac0
    [&amp;lt;ffffffffa540acf3&amp;gt;] jffs2_do_fill_super+0x383/0xc30
    [&amp;lt;ffffffffa540c00a&amp;gt;] jffs2_fill_super+0x2ea/0x4c0
    [...]
--------------------------------------------&lt;/p&gt;
&lt;p&gt;This is because the resources allo…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-49277</guid>
    </item>
    <item>
      <title>GHSA-rfv9-hghg-chfq</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-rfv9-hghg-chfq</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;jffs2: fix memory leak in jffs2_do_mount_fs&lt;/p&gt;
&lt;p&gt;If jffs2_build_filesystem() in jffs2_do_mount_fs() returns an error,
we can observe the following kmemleak report:&lt;/p&gt;
&lt;p&gt;--------------------------------------------
unreferenced object 0xffff88811b25a640 (size 64):
  comm &amp;#34;mount&amp;#34;, pid 691, jiffies 4294957728 (age 71.952s)
  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:
    [&amp;lt;ffffffffa493be24&amp;gt;] kmem_cache_alloc_trace+0x584/0x880
    [&amp;lt;ffffffffa5423a06&amp;gt;] jffs2_sum_init+0x86/0x130
    [&amp;lt;ffffffffa5400e58&amp;gt;] jffs2_do_mount_fs+0x798/0xac0
    [&amp;lt;ffffffffa540acf3&amp;gt;] jffs2_do_fill_super+0x383/0xc30
    [&amp;lt;ffffffffa540c00a&amp;gt;] jffs2_fill_super+0x2ea/0x4c0
    [...]
unreferenced object 0xffff88812c760000 (size 65536):
  comm &amp;#34;mount&amp;#34;, pid 691, jiffies 4294957728 (age 71.952s)
  hex dump (first 32 bytes):
    bb bb bb bb bb bb bb bb bb bb bb bb bb bb bb bb  ................
    bb bb bb bb bb bb bb bb bb bb bb bb bb bb bb bb  ................
  backtrace:
    [&amp;lt;ffffffffa493a449&amp;gt;] __kmalloc+0x6b9/0x910
    [&amp;lt;ffffffffa5423a57&amp;gt;] jffs2_sum_init+0xd7/0x130
    [&amp;lt;ffffffffa5400e58&amp;gt;] jffs2_do_mount_fs+0x798/0xac0
    [&amp;lt;ffffffffa540acf3&amp;gt;] jffs2_do_fill_super+0x383/0xc30
    [&amp;lt;ffffffffa540c00a&amp;gt;] jffs2_fill_super+0x2ea/0x4c0
    [...]
--------------------------------------------&lt;/p&gt;
&lt;p&gt;This is because the resources allo…&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;jffs2: fix memory leak in jffs2_do_mount_fs&lt;/p&gt;
&lt;p&gt;If jffs2_build_filesystem() in jffs2_do_mount_fs() returns an error,
we can observe the following kmemleak report:&lt;/p&gt;
&lt;p&gt;--------------------------------------------
unreferenced object 0xffff88811b25a640 (size 64):
  comm &amp;#34;mount&amp;#34;, pid 691, jiffies 4294957728 (age 71.952s)
  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:
    [&amp;lt;ffffffffa493be24&amp;gt;] kmem_cache_alloc_trace+0x584/0x880
    [&amp;lt;ffffffffa5423a06&amp;gt;] jffs2_sum_init+0x86/0x130
    [&amp;lt;ffffffffa5400e58&amp;gt;] jffs2_do_mount_fs+0x798/0xac0
    [&amp;lt;ffffffffa540acf3&amp;gt;] jffs2_do_fill_super+0x383/0xc30
    [&amp;lt;ffffffffa540c00a&amp;gt;] jffs2_fill_super+0x2ea/0x4c0
    [...]
unreferenced object 0xffff88812c760000 (size 65536):
  comm &amp;#34;mount&amp;#34;, pid 691, jiffies 4294957728 (age 71.952s)
  hex dump (first 32 bytes):
    bb bb bb bb bb bb bb bb bb bb bb bb bb bb bb bb  ................
    bb bb bb bb bb bb bb bb bb bb bb bb bb bb bb bb  ................
  backtrace:
    [&amp;lt;ffffffffa493a449&amp;gt;] __kmalloc+0x6b9/0x910
    [&amp;lt;ffffffffa5423a57&amp;gt;] jffs2_sum_init+0xd7/0x130
    [&amp;lt;ffffffffa5400e58&amp;gt;] jffs2_do_mount_fs+0x798/0xac0
    [&amp;lt;ffffffffa540acf3&amp;gt;] jffs2_do_fill_super+0x383/0xc30
    [&amp;lt;ffffffffa540c00a&amp;gt;] jffs2_fill_super+0x2ea/0x4c0
    [...]
--------------------------------------------&lt;/p&gt;
&lt;p&gt;This is because the resources allo…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-rfv9-hghg-chfq</guid>
    </item>
    <item>
      <title>OESA-2025-1317 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-1317</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):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ubi: Fix race condition between ctrl_cdev_ioctl and ubi_cdev_ioctl&lt;/p&gt;
&lt;p&gt;Hulk Robot reported a KASAN report about use-after-free:
 ==================================================================
 BUG: KASAN: use-after-free in __list_del_entry_valid+0x13d/0x160
 Read of size 8 at addr ffff888035e37d98 by task ubiattach/1385
 [...]
 Call Trace:
  klist_dec_and_del+0xa7/0x4a0
  klist_put+0xc7/0x1a0
  device_del+0x4d4/0xed0
  cdev_device_del+0x1a/0x80
  ubi_attach_mtd_dev+0x2951/0x34b0 [ubi]
  ctrl_cdev_ioctl+0x286/0x2f0 [ubi]&lt;/p&gt;
&lt;p&gt;Allocated by task 1414:
  device_add+0x60a/0x18b0
  cdev_device_add+0x103/0x170
  ubi_create_volume+0x1118/0x1a10 [ubi]
  ubi_cdev_ioctl+0xb7f/0x1ba0 [ubi]&lt;/p&gt;
&lt;p&gt;Freed by task 1385:
  cdev_device_del+0x1a/0x80
  ubi_remove_volume+0x438/0x6c0 [ubi]
  ubi_cdev_ioctl+0xbf4/0x1ba0 [ubi]
 [...]
 ==================================================================&lt;/p&gt;
&lt;p&gt;The lock held by ctrl_cdev_ioctl is ubi_devices_mutex, but the lock held
by ubi_cdev_ioctl is ubi-&amp;amp;gt;device_mutex. Therefore, the two locks can be
concurrent.&lt;/p&gt;
&lt;p&gt;ctrl_cdev_ioctl contains two operations: ubi_attach and ubi_detach.
ubi_detach is bug-free because it uses reference counting to prevent
concurrency. However, uif_init and uif_close in ubi_attach may race with
ubi_cdev_ioctl.&lt;/p&gt;
&lt;p&gt;uif_init will race with ubi_cdev_ioctl as in the following stack.
           cpu1…&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):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ubi: Fix race condition between ctrl_cdev_ioctl and ubi_cdev_ioctl&lt;/p&gt;
&lt;p&gt;Hulk Robot reported a KASAN report about use-after-free:
 ==================================================================
 BUG: KASAN: use-after-free in __list_del_entry_valid+0x13d/0x160
 Read of size 8 at addr ffff888035e37d98 by task ubiattach/1385
 [...]
 Call Trace:
  klist_dec_and_del+0xa7/0x4a0
  klist_put+0xc7/0x1a0
  device_del+0x4d4/0xed0
  cdev_device_del+0x1a/0x80
  ubi_attach_mtd_dev+0x2951/0x34b0 [ubi]
  ctrl_cdev_ioctl+0x286/0x2f0 [ubi]&lt;/p&gt;
&lt;p&gt;Allocated by task 1414:
  device_add+0x60a/0x18b0
  cdev_device_add+0x103/0x170
  ubi_create_volume+0x1118/0x1a10 [ubi]
  ubi_cdev_ioctl+0xb7f/0x1ba0 [ubi]&lt;/p&gt;
&lt;p&gt;Freed by task 1385:
  cdev_device_del+0x1a/0x80
  ubi_remove_volume+0x438/0x6c0 [ubi]
  ubi_cdev_ioctl+0xbf4/0x1ba0 [ubi]
 [...]
 ==================================================================&lt;/p&gt;
&lt;p&gt;The lock held by ctrl_cdev_ioctl is ubi_devices_mutex, but the lock held
by ubi_cdev_ioctl is ubi-&amp;amp;gt;device_mutex. Therefore, the two locks can be
concurrent.&lt;/p&gt;
&lt;p&gt;ctrl_cdev_ioctl contains two operations: ubi_attach and ubi_detach.
ubi_detach is bug-free because it uses reference counting to prevent
concurrency. However, uif_init and uif_close in ubi_attach may race with
ubi_cdev_ioctl.&lt;/p&gt;
&lt;p&gt;uif_init will race with ubi_cdev_ioctl as in the following stack.
           cpu1…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-1317</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-2022-49277</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49277</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, 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 and 138 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: jffs2: fix memory leak in jffs2_do_mount_fs If jffs2_build_filesystem() in jffs2_do_mount_fs() returns an error, we can observe the following kmemleak report: -------------------------------------------- unreferenced object 0xffff88811b25a640 (size 64):   comm &amp;#34;mount&amp;#34;, pid 691, jiffies 4294957728 (age 71.952s)   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:     [&amp;lt;ffffffffa493be24&amp;gt;] kmem_cache_alloc_trace+0x584/0x880     [&amp;lt;ffffffffa5423a06&amp;gt;] jffs2_sum_init+0x86/0x130     [&amp;lt;ffffffffa5400e58&amp;gt;] jffs2_do_mount_fs+0x798/0xac0     [&amp;lt;ffffffffa540acf3&amp;gt;] jffs2_do_fill_super+0x383/0xc30     [&amp;lt;ffffffffa540c00a&amp;gt;] jffs2_fill_super+0x2ea/0x4c0     [...] unreferenced object 0xffff88812c760000 (size 65536):   comm &amp;#34;mount&amp;#34;, pid 691, jiffies 4294957728 (age 71.952s)   hex dump (first 32 bytes):     bb bb bb bb bb bb bb bb bb bb bb bb bb bb bb bb  ................     bb bb bb bb bb bb bb bb bb bb bb bb bb bb bb bb  ................   backtrace:     [&amp;lt;ffffffffa493a449&amp;gt;] __kmalloc+0x6b9/0x910     [&amp;lt;ffffffffa5423a57&amp;gt;] jffs2_sum_init+0xd7/0x130     [&amp;lt;ffffffffa5400e58&amp;gt;] jffs2_do_mount_fs+0x798/0xac0     [&amp;lt;ffffffffa540acf3&amp;gt;] jffs2_do_fill_super+0x383/0xc30     [&amp;lt;ffffffffa540c00a&amp;gt;] jffs2_fill_super+0x2ea/0x4c0     [...] -------------------------------------------- This is because the resources allocate…&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, 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 and 138 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: jffs2: fix memory leak in jffs2_do_mount_fs If jffs2_build_filesystem() in jffs2_do_mount_fs() returns an error, we can observe the following kmemleak report: -------------------------------------------- unreferenced object 0xffff88811b25a640 (size 64):   comm &amp;#34;mount&amp;#34;, pid 691, jiffies 4294957728 (age 71.952s)   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:     [&amp;lt;ffffffffa493be24&amp;gt;] kmem_cache_alloc_trace+0x584/0x880     [&amp;lt;ffffffffa5423a06&amp;gt;] jffs2_sum_init+0x86/0x130     [&amp;lt;ffffffffa5400e58&amp;gt;] jffs2_do_mount_fs+0x798/0xac0     [&amp;lt;ffffffffa540acf3&amp;gt;] jffs2_do_fill_super+0x383/0xc30     [&amp;lt;ffffffffa540c00a&amp;gt;] jffs2_fill_super+0x2ea/0x4c0     [...] unreferenced object 0xffff88812c760000 (size 65536):   comm &amp;#34;mount&amp;#34;, pid 691, jiffies 4294957728 (age 71.952s)   hex dump (first 32 bytes):     bb bb bb bb bb bb bb bb bb bb bb bb bb bb bb bb  ................     bb bb bb bb bb bb bb bb bb bb bb bb bb bb bb bb  ................   backtrace:     [&amp;lt;ffffffffa493a449&amp;gt;] __kmalloc+0x6b9/0x910     [&amp;lt;ffffffffa5423a57&amp;gt;] jffs2_sum_init+0xd7/0x130     [&amp;lt;ffffffffa5400e58&amp;gt;] jffs2_do_mount_fs+0x798/0xac0     [&amp;lt;ffffffffa540acf3&amp;gt;] jffs2_do_fill_super+0x383/0xc30     [&amp;lt;ffffffffa540c00a&amp;gt;] jffs2_fill_super+0x2ea/0x4c0     [...] -------------------------------------------- This is because the resources allocate…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49277</guid>
    </item>
  </channel>
</rss>
