<?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 11:05:44 +0000</lastBuildDate>
    <item>
      <title>Withdrawn: BELL-CVE-2025-71312 — CVE-2025-71312 does not affect BellSoft software</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-71312</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2025-71312</guid>
    </item>
    <item>
      <title>EUVD-2026-321880</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-321880</link>
      <description>EUVD-2026-321880</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-321880</guid>
    </item>
    <item>
      <title>fkie_cve-2025-71312</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-71312</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fs/ntfs3: fix ntfs_mount_options leak in ntfs_fill_super()&lt;/p&gt;
&lt;p&gt;In ntfs_fill_super(), the fc-&amp;gt;fs_private pointer is set to NULL without
first freeing the memory it points to. This causes the subsequent call to
ntfs_fs_free() to skip freeing the ntfs_mount_options structure.&lt;/p&gt;
&lt;p&gt;This results in a kmemleak report:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xff1100015378b800 (size 32):
    comm &amp;#34;mount&amp;#34;, pid 582, jiffies 4294890685
    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 ed ff ed ff 00 04 00 00  ................
    backtrace (crc ed541d8c):
      __kmalloc_cache_noprof+0x424/0x5a0
      __ntfs_init_fs_context+0x47/0x590
      alloc_fs_context+0x5d8/0x960
      __x64_sys_fsopen+0xb1/0x190
      do_syscall_64+0x50/0x1f0
      entry_SYSCALL_64_after_hwframe+0x76/0x7e&lt;/p&gt;
&lt;p&gt;This issue can be reproduced using the following commands:
        fallocate -l 100M test.file
        mount test.file /tmp/test&lt;/p&gt;
&lt;p&gt;Since sbi-&amp;gt;options is duplicated from fc-&amp;gt;fs_private and does not
directly use the memory allocated for fs_private, it is unnecessary to
set fc-&amp;gt;fs_private to NULL.&lt;/p&gt;
&lt;p&gt;Additionally, this patch simplifies the code by utilizing the helper
function put_mount_options() instead of open-coding the cleanup logic.&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;fs/ntfs3: fix ntfs_mount_options leak in ntfs_fill_super()&lt;/p&gt;
&lt;p&gt;In ntfs_fill_super(), the fc-&amp;gt;fs_private pointer is set to NULL without
first freeing the memory it points to. This causes the subsequent call to
ntfs_fs_free() to skip freeing the ntfs_mount_options structure.&lt;/p&gt;
&lt;p&gt;This results in a kmemleak report:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xff1100015378b800 (size 32):
    comm &amp;#34;mount&amp;#34;, pid 582, jiffies 4294890685
    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 ed ff ed ff 00 04 00 00  ................
    backtrace (crc ed541d8c):
      __kmalloc_cache_noprof+0x424/0x5a0
      __ntfs_init_fs_context+0x47/0x590
      alloc_fs_context+0x5d8/0x960
      __x64_sys_fsopen+0xb1/0x190
      do_syscall_64+0x50/0x1f0
      entry_SYSCALL_64_after_hwframe+0x76/0x7e&lt;/p&gt;
&lt;p&gt;This issue can be reproduced using the following commands:
        fallocate -l 100M test.file
        mount test.file /tmp/test&lt;/p&gt;
&lt;p&gt;Since sbi-&amp;gt;options is duplicated from fc-&amp;gt;fs_private and does not
directly use the memory allocated for fs_private, it is unnecessary to
set fc-&amp;gt;fs_private to NULL.&lt;/p&gt;
&lt;p&gt;Additionally, this patch simplifies the code by utilizing the helper
function put_mount_options() instead of open-coding the cleanup logic.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-71312</guid>
    </item>
    <item>
      <title>GHSA-w58m-8mj8-hh8w</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-w58m-8mj8-hh8w</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fs/ntfs3: fix ntfs_mount_options leak in ntfs_fill_super()&lt;/p&gt;
&lt;p&gt;In ntfs_fill_super(), the fc-&amp;gt;fs_private pointer is set to NULL without
first freeing the memory it points to. This causes the subsequent call to
ntfs_fs_free() to skip freeing the ntfs_mount_options structure.&lt;/p&gt;
&lt;p&gt;This results in a kmemleak report:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xff1100015378b800 (size 32):
    comm &amp;#34;mount&amp;#34;, pid 582, jiffies 4294890685
    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 ed ff ed ff 00 04 00 00  ................
    backtrace (crc ed541d8c):
      __kmalloc_cache_noprof+0x424/0x5a0
      __ntfs_init_fs_context+0x47/0x590
      alloc_fs_context+0x5d8/0x960
      __x64_sys_fsopen+0xb1/0x190
      do_syscall_64+0x50/0x1f0
      entry_SYSCALL_64_after_hwframe+0x76/0x7e&lt;/p&gt;
&lt;p&gt;This issue can be reproduced using the following commands:
        fallocate -l 100M test.file
        mount test.file /tmp/test&lt;/p&gt;
&lt;p&gt;Since sbi-&amp;gt;options is duplicated from fc-&amp;gt;fs_private and does not
directly use the memory allocated for fs_private, it is unnecessary to
set fc-&amp;gt;fs_private to NULL.&lt;/p&gt;
&lt;p&gt;Additionally, this patch simplifies the code by utilizing the helper
function put_mount_options() instead of open-coding the cleanup logic.&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;fs/ntfs3: fix ntfs_mount_options leak in ntfs_fill_super()&lt;/p&gt;
&lt;p&gt;In ntfs_fill_super(), the fc-&amp;gt;fs_private pointer is set to NULL without
first freeing the memory it points to. This causes the subsequent call to
ntfs_fs_free() to skip freeing the ntfs_mount_options structure.&lt;/p&gt;
&lt;p&gt;This results in a kmemleak report:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xff1100015378b800 (size 32):
    comm &amp;#34;mount&amp;#34;, pid 582, jiffies 4294890685
    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 ed ff ed ff 00 04 00 00  ................
    backtrace (crc ed541d8c):
      __kmalloc_cache_noprof+0x424/0x5a0
      __ntfs_init_fs_context+0x47/0x590
      alloc_fs_context+0x5d8/0x960
      __x64_sys_fsopen+0xb1/0x190
      do_syscall_64+0x50/0x1f0
      entry_SYSCALL_64_after_hwframe+0x76/0x7e&lt;/p&gt;
&lt;p&gt;This issue can be reproduced using the following commands:
        fallocate -l 100M test.file
        mount test.file /tmp/test&lt;/p&gt;
&lt;p&gt;Since sbi-&amp;gt;options is duplicated from fc-&amp;gt;fs_private and does not
directly use the memory allocated for fs_private, it is unnecessary to
set fc-&amp;gt;fs_private to NULL.&lt;/p&gt;
&lt;p&gt;Additionally, this patch simplifies the code by utilizing the helper
function put_mount_options() instead of open-coding the cleanup logic.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-w58m-8mj8-hh8w</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-71312</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-71312</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 85 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: fix ntfs_mount_options leak in ntfs_fill_super() In ntfs_fill_super(), the fc-&amp;gt;fs_private pointer is set to NULL without first freeing the memory it points to. This causes the subsequent call to ntfs_fs_free() to skip freeing the ntfs_mount_options structure. This results in a kmemleak report:   unreferenced object 0xff1100015378b800 (size 32):     comm &amp;#34;mount&amp;#34;, pid 582, jiffies 4294890685     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 ed ff ed ff 00 04 00 00  ................     backtrace (crc ed541d8c):       __kmalloc_cache_noprof+0x424/0x5a0       __ntfs_init_fs_context+0x47/0x590       alloc_fs_context+0x5d8/0x960       __x64_sys_fsopen+0xb1/0x190       do_syscall_64+0x50/0x1f0       entry_SYSCALL_64_after_hwframe+0x76/0x7e This issue can be reproduced using the following commands:         fallocate -l 100M test.file         mount test.file /tmp/test Since sbi-&amp;gt;options is duplicated from fc-&amp;gt;fs_private and does not directly use the memory allocated for fs_private, it is unnecessary to set fc-&amp;gt;fs_private to NULL. Additionally, this patch simplifies the code by utilizing the helper function put_mount_options() instead of open-coding the cleanup logic.&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 85 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: fix ntfs_mount_options leak in ntfs_fill_super() In ntfs_fill_super(), the fc-&amp;gt;fs_private pointer is set to NULL without first freeing the memory it points to. This causes the subsequent call to ntfs_fs_free() to skip freeing the ntfs_mount_options structure. This results in a kmemleak report:   unreferenced object 0xff1100015378b800 (size 32):     comm &amp;#34;mount&amp;#34;, pid 582, jiffies 4294890685     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 ed ff ed ff 00 04 00 00  ................     backtrace (crc ed541d8c):       __kmalloc_cache_noprof+0x424/0x5a0       __ntfs_init_fs_context+0x47/0x590       alloc_fs_context+0x5d8/0x960       __x64_sys_fsopen+0xb1/0x190       do_syscall_64+0x50/0x1f0       entry_SYSCALL_64_after_hwframe+0x76/0x7e This issue can be reproduced using the following commands:         fallocate -l 100M test.file         mount test.file /tmp/test Since sbi-&amp;gt;options is duplicated from fc-&amp;gt;fs_private and does not directly use the memory allocated for fs_private, it is unnecessary to set fc-&amp;gt;fs_private to NULL. Additionally, this patch simplifies the code by utilizing the helper function put_mount_options() instead of open-coding the cleanup logic.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-71312</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-1700 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1700</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht näher spezifizierte Auswirkungen zu erzielen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht näher spezifizierte Auswirkungen zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1700</guid>
    </item>
  </channel>
</rss>
