<?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>Fri, 02 Oct 2026 10:41:35 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-04863</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-04863</link>
      <description>bdu:2026-04863</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-04863</guid>
    </item>
    <item>
      <title>certfr-2025-avi-1032 — 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-1032</link>
      <description>certfr-2025-avi-1032</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-1032</guid>
    </item>
    <item>
      <title>EUVD-2026-311165</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-311165</link>
      <description>EUVD-2026-311165</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-311165</guid>
    </item>
    <item>
      <title>fkie_cve-2022-50334</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-50334</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;hugetlbfs: fix null-ptr-deref in hugetlbfs_parse_param()&lt;/p&gt;
&lt;p&gt;Syzkaller reports a null-ptr-deref bug as follows:
======================================================
KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]
RIP: 0010:hugetlbfs_parse_param+0x1dd/0x8e0 fs/hugetlbfs/inode.c:1380
[...]
Call Trace:
 &amp;lt;TASK&amp;gt;
 vfs_parse_fs_param fs/fs_context.c:148 [inline]
 vfs_parse_fs_param+0x1f9/0x3c0 fs/fs_context.c:129
 vfs_parse_fs_string+0xdb/0x170 fs/fs_context.c:191
 generic_parse_monolithic+0x16f/0x1f0 fs/fs_context.c:231
 do_new_mount fs/namespace.c:3036 [inline]
 path_mount+0x12de/0x1e20 fs/namespace.c:3370
 do_mount fs/namespace.c:3383 [inline]
 __do_sys_mount fs/namespace.c:3591 [inline]
 __se_sys_mount fs/namespace.c:3568 [inline]
 __x64_sys_mount+0x27f/0x300 fs/namespace.c:3568
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
 [...]
 &amp;lt;/TASK&amp;gt;
======================================================&lt;/p&gt;
&lt;p&gt;According to commit &amp;#34;vfs: parse: deal with zero length string value&amp;#34;,
kernel will set the param-&amp;gt;string to null pointer in vfs_parse_fs_string()
if fs string has zero length.&lt;/p&gt;
&lt;p&gt;Yet the problem is that, hugetlbfs_parse_param() will dereference the
param-&amp;gt;string, without checking whether it is a null pointer.  To be more
specific, if hugetlbfs_parse_param() parses an illegal mount parameter,
such as &amp;#34;si…&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;hugetlbfs: fix null-ptr-deref in hugetlbfs_parse_param()&lt;/p&gt;
&lt;p&gt;Syzkaller reports a null-ptr-deref bug as follows:
======================================================
KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]
RIP: 0010:hugetlbfs_parse_param+0x1dd/0x8e0 fs/hugetlbfs/inode.c:1380
[...]
Call Trace:
 &amp;lt;TASK&amp;gt;
 vfs_parse_fs_param fs/fs_context.c:148 [inline]
 vfs_parse_fs_param+0x1f9/0x3c0 fs/fs_context.c:129
 vfs_parse_fs_string+0xdb/0x170 fs/fs_context.c:191
 generic_parse_monolithic+0x16f/0x1f0 fs/fs_context.c:231
 do_new_mount fs/namespace.c:3036 [inline]
 path_mount+0x12de/0x1e20 fs/namespace.c:3370
 do_mount fs/namespace.c:3383 [inline]
 __do_sys_mount fs/namespace.c:3591 [inline]
 __se_sys_mount fs/namespace.c:3568 [inline]
 __x64_sys_mount+0x27f/0x300 fs/namespace.c:3568
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
 [...]
 &amp;lt;/TASK&amp;gt;
======================================================&lt;/p&gt;
&lt;p&gt;According to commit &amp;#34;vfs: parse: deal with zero length string value&amp;#34;,
kernel will set the param-&amp;gt;string to null pointer in vfs_parse_fs_string()
if fs string has zero length.&lt;/p&gt;
&lt;p&gt;Yet the problem is that, hugetlbfs_parse_param() will dereference the
param-&amp;gt;string, without checking whether it is a null pointer.  To be more
specific, if hugetlbfs_parse_param() parses an illegal mount parameter,
such as &amp;#34;si…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-50334</guid>
    </item>
    <item>
      <title>GHSA-8wrh-ch6p-2682</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-8wrh-ch6p-2682</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;hugetlbfs: fix null-ptr-deref in hugetlbfs_parse_param()&lt;/p&gt;
&lt;p&gt;Syzkaller reports a null-ptr-deref bug as follows:
======================================================
KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]
RIP: 0010:hugetlbfs_parse_param+0x1dd/0x8e0 fs/hugetlbfs/inode.c:1380
[...]
Call Trace:
 &amp;lt;TASK&amp;gt;
 vfs_parse_fs_param fs/fs_context.c:148 [inline]
 vfs_parse_fs_param+0x1f9/0x3c0 fs/fs_context.c:129
 vfs_parse_fs_string+0xdb/0x170 fs/fs_context.c:191
 generic_parse_monolithic+0x16f/0x1f0 fs/fs_context.c:231
 do_new_mount fs/namespace.c:3036 [inline]
 path_mount+0x12de/0x1e20 fs/namespace.c:3370
 do_mount fs/namespace.c:3383 [inline]
 __do_sys_mount fs/namespace.c:3591 [inline]
 __se_sys_mount fs/namespace.c:3568 [inline]
 __x64_sys_mount+0x27f/0x300 fs/namespace.c:3568
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
 [...]
 &amp;lt;/TASK&amp;gt;
======================================================&lt;/p&gt;
&lt;p&gt;According to commit &amp;#34;vfs: parse: deal with zero length string value&amp;#34;,
kernel will set the param-&amp;gt;string to null pointer in vfs_parse_fs_string()
if fs string has zero length.&lt;/p&gt;
&lt;p&gt;Yet the problem is that, hugetlbfs_parse_param() will dereference the
param-&amp;gt;string, without checking whether it is a null pointer.  To be more
specific, if hugetlbfs_parse_param() parses an illegal mount parameter,
such as &amp;#34;si…&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;hugetlbfs: fix null-ptr-deref in hugetlbfs_parse_param()&lt;/p&gt;
&lt;p&gt;Syzkaller reports a null-ptr-deref bug as follows:
======================================================
KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]
RIP: 0010:hugetlbfs_parse_param+0x1dd/0x8e0 fs/hugetlbfs/inode.c:1380
[...]
Call Trace:
 &amp;lt;TASK&amp;gt;
 vfs_parse_fs_param fs/fs_context.c:148 [inline]
 vfs_parse_fs_param+0x1f9/0x3c0 fs/fs_context.c:129
 vfs_parse_fs_string+0xdb/0x170 fs/fs_context.c:191
 generic_parse_monolithic+0x16f/0x1f0 fs/fs_context.c:231
 do_new_mount fs/namespace.c:3036 [inline]
 path_mount+0x12de/0x1e20 fs/namespace.c:3370
 do_mount fs/namespace.c:3383 [inline]
 __do_sys_mount fs/namespace.c:3591 [inline]
 __se_sys_mount fs/namespace.c:3568 [inline]
 __x64_sys_mount+0x27f/0x300 fs/namespace.c:3568
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
 [...]
 &amp;lt;/TASK&amp;gt;
======================================================&lt;/p&gt;
&lt;p&gt;According to commit &amp;#34;vfs: parse: deal with zero length string value&amp;#34;,
kernel will set the param-&amp;gt;string to null pointer in vfs_parse_fs_string()
if fs string has zero length.&lt;/p&gt;
&lt;p&gt;Yet the problem is that, hugetlbfs_parse_param() will dereference the
param-&amp;gt;string, without checking whether it is a null pointer.  To be more
specific, if hugetlbfs_parse_param() parses an illegal mount parameter,
such as &amp;#34;si…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-8wrh-ch6p-2682</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:4135-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:4135-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:4135-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-50334</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50334</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, 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 and 158 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: hugetlbfs: fix null-ptr-deref in hugetlbfs_parse_param() Syzkaller reports a null-ptr-deref bug as follows: ====================================================== KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] RIP: 0010:hugetlbfs_parse_param+0x1dd/0x8e0 fs/hugetlbfs/inode.c:1380 [...] Call Trace:  &amp;lt;TASK&amp;gt;  vfs_parse_fs_param fs/fs_context.c:148 [inline]  vfs_parse_fs_param+0x1f9/0x3c0 fs/fs_context.c:129  vfs_parse_fs_string+0xdb/0x170 fs/fs_context.c:191  generic_parse_monolithic+0x16f/0x1f0 fs/fs_context.c:231  do_new_mount fs/namespace.c:3036 [inline]  path_mount+0x12de/0x1e20 fs/namespace.c:3370  do_mount fs/namespace.c:3383 [inline]  __do_sys_mount fs/namespace.c:3591 [inline]  __se_sys_mount fs/namespace.c:3568 [inline]  __x64_sys_mount+0x27f/0x300 fs/namespace.c:3568  do_syscall_x64 arch/x86/entry/common.c:50 [inline]  do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80  entry_SYSCALL_64_after_hwframe+0x63/0xcd  [...]  &amp;lt;/TASK&amp;gt; ====================================================== According to commit &amp;#34;vfs: parse: deal with zero length string value&amp;#34;, kernel will set the param-&amp;gt;string to null pointer in vfs_parse_fs_string() if fs string has zero length. Yet the problem is that, hugetlbfs_parse_param() will dereference the param-&amp;gt;string, without checking whether it is a null pointer.  To be more specific, if hugetlbfs_parse_param() parses an illegal mount parameter, such as &amp;#34;size=,…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, 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 and 158 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: hugetlbfs: fix null-ptr-deref in hugetlbfs_parse_param() Syzkaller reports a null-ptr-deref bug as follows: ====================================================== KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] RIP: 0010:hugetlbfs_parse_param+0x1dd/0x8e0 fs/hugetlbfs/inode.c:1380 [...] Call Trace:  &amp;lt;TASK&amp;gt;  vfs_parse_fs_param fs/fs_context.c:148 [inline]  vfs_parse_fs_param+0x1f9/0x3c0 fs/fs_context.c:129  vfs_parse_fs_string+0xdb/0x170 fs/fs_context.c:191  generic_parse_monolithic+0x16f/0x1f0 fs/fs_context.c:231  do_new_mount fs/namespace.c:3036 [inline]  path_mount+0x12de/0x1e20 fs/namespace.c:3370  do_mount fs/namespace.c:3383 [inline]  __do_sys_mount fs/namespace.c:3591 [inline]  __se_sys_mount fs/namespace.c:3568 [inline]  __x64_sys_mount+0x27f/0x300 fs/namespace.c:3568  do_syscall_x64 arch/x86/entry/common.c:50 [inline]  do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80  entry_SYSCALL_64_after_hwframe+0x63/0xcd  [...]  &amp;lt;/TASK&amp;gt; ====================================================== According to commit &amp;#34;vfs: parse: deal with zero length string value&amp;#34;, kernel will set the param-&amp;gt;string to null pointer in vfs_parse_fs_string() if fs string has zero length. Yet the problem is that, hugetlbfs_parse_param() will dereference the param-&amp;gt;string, without checking whether it is a null pointer.  To be more specific, if hugetlbfs_parse_param() parses an illegal mount parameter, such as &amp;#34;size=,…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50334</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2053 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2053</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher beschriebene 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 nicht näher beschriebene Auswirkungen zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2053</guid>
    </item>
  </channel>
</rss>
