<?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 10:43:06 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-10634</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-10634</link>
      <description>bdu:2026-10634</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-10634</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-68219</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-68219</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-68219</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0316 — De multiples vulnérabilités ont été découvertes dans les produits VMware. Elles permettent à un attaquant de provoquer…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0316</link>
      <description>certfr-2026-avi-0316</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0316</guid>
    </item>
    <item>
      <title>EUVD-2026-315059</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-315059</link>
      <description>EUVD-2026-315059</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-315059</guid>
    </item>
    <item>
      <title>fkie_cve-2025-68219</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-68219</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;cifs: fix memory leak in smb3_fs_context_parse_param error path&lt;/p&gt;
&lt;p&gt;Add proper cleanup of ctx-&amp;gt;source and fc-&amp;gt;source to the
cifs_parse_mount_err error handler. This ensures that memory allocated
for the source strings is correctly freed on all error paths, matching
the cleanup already performed in the success path by
smb3_cleanup_fs_context_contents().
Pointers are also set to NULL after freeing to prevent potential
double-free issues.&lt;/p&gt;
&lt;p&gt;This change fixes a memory leak originally detected by syzbot. The
leak occurred when processing Opt_source mount options if an error
happened after ctx-&amp;gt;source and fc-&amp;gt;source were successfully
allocated but before the function completed.&lt;/p&gt;
&lt;p&gt;The specific leak sequence was:
1. ctx-&amp;gt;source = smb3_fs_context_fullpath(ctx, &amp;#39;/&amp;#39;) allocates memory
2. fc-&amp;gt;source = kstrdup(ctx-&amp;gt;source, GFP_KERNEL) allocates more memory
3. A subsequent error jumps to cifs_parse_mount_err
4. The old error handler freed passwords but not the source strings,
causing the memory to leak.&lt;/p&gt;
&lt;p&gt;This issue was not addressed by commit e8c73eb7db0a (&amp;#34;cifs: client:
fix memory leak in smb3_fs_context_parse_param&amp;#34;), which only fixed
leaks from repeated fsconfig() calls but not this error path.&lt;/p&gt;
&lt;p&gt;Patch updated with minor change suggested by kernel test robot&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;cifs: fix memory leak in smb3_fs_context_parse_param error path&lt;/p&gt;
&lt;p&gt;Add proper cleanup of ctx-&amp;gt;source and fc-&amp;gt;source to the
cifs_parse_mount_err error handler. This ensures that memory allocated
for the source strings is correctly freed on all error paths, matching
the cleanup already performed in the success path by
smb3_cleanup_fs_context_contents().
Pointers are also set to NULL after freeing to prevent potential
double-free issues.&lt;/p&gt;
&lt;p&gt;This change fixes a memory leak originally detected by syzbot. The
leak occurred when processing Opt_source mount options if an error
happened after ctx-&amp;gt;source and fc-&amp;gt;source were successfully
allocated but before the function completed.&lt;/p&gt;
&lt;p&gt;The specific leak sequence was:
1. ctx-&amp;gt;source = smb3_fs_context_fullpath(ctx, &amp;#39;/&amp;#39;) allocates memory
2. fc-&amp;gt;source = kstrdup(ctx-&amp;gt;source, GFP_KERNEL) allocates more memory
3. A subsequent error jumps to cifs_parse_mount_err
4. The old error handler freed passwords but not the source strings,
causing the memory to leak.&lt;/p&gt;
&lt;p&gt;This issue was not addressed by commit e8c73eb7db0a (&amp;#34;cifs: client:
fix memory leak in smb3_fs_context_parse_param&amp;#34;), which only fixed
leaks from repeated fsconfig() calls but not this error path.&lt;/p&gt;
&lt;p&gt;Patch updated with minor change suggested by kernel test robot&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-68219</guid>
    </item>
    <item>
      <title>GHSA-6qvg-p925-pxr9</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-6qvg-p925-pxr9</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;cifs: fix memory leak in smb3_fs_context_parse_param error path&lt;/p&gt;
&lt;p&gt;Add proper cleanup of ctx-&amp;gt;source and fc-&amp;gt;source to the
cifs_parse_mount_err error handler. This ensures that memory allocated
for the source strings is correctly freed on all error paths, matching
the cleanup already performed in the success path by
smb3_cleanup_fs_context_contents().
Pointers are also set to NULL after freeing to prevent potential
double-free issues.&lt;/p&gt;
&lt;p&gt;This change fixes a memory leak originally detected by syzbot. The
leak occurred when processing Opt_source mount options if an error
happened after ctx-&amp;gt;source and fc-&amp;gt;source were successfully
allocated but before the function completed.&lt;/p&gt;
&lt;p&gt;The specific leak sequence was:
1. ctx-&amp;gt;source = smb3_fs_context_fullpath(ctx, &amp;#39;/&amp;#39;) allocates memory
2. fc-&amp;gt;source = kstrdup(ctx-&amp;gt;source, GFP_KERNEL) allocates more memory
3. A subsequent error jumps to cifs_parse_mount_err
4. The old error handler freed passwords but not the source strings,
causing the memory to leak.&lt;/p&gt;
&lt;p&gt;This issue was not addressed by commit e8c73eb7db0a (&amp;#34;cifs: client:
fix memory leak in smb3_fs_context_parse_param&amp;#34;), which only fixed
leaks from repeated fsconfig() calls but not this error path.&lt;/p&gt;
&lt;p&gt;Patch updated with minor change suggested by kernel test robot&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;cifs: fix memory leak in smb3_fs_context_parse_param error path&lt;/p&gt;
&lt;p&gt;Add proper cleanup of ctx-&amp;gt;source and fc-&amp;gt;source to the
cifs_parse_mount_err error handler. This ensures that memory allocated
for the source strings is correctly freed on all error paths, matching
the cleanup already performed in the success path by
smb3_cleanup_fs_context_contents().
Pointers are also set to NULL after freeing to prevent potential
double-free issues.&lt;/p&gt;
&lt;p&gt;This change fixes a memory leak originally detected by syzbot. The
leak occurred when processing Opt_source mount options if an error
happened after ctx-&amp;gt;source and fc-&amp;gt;source were successfully
allocated but before the function completed.&lt;/p&gt;
&lt;p&gt;The specific leak sequence was:
1. ctx-&amp;gt;source = smb3_fs_context_fullpath(ctx, &amp;#39;/&amp;#39;) allocates memory
2. fc-&amp;gt;source = kstrdup(ctx-&amp;gt;source, GFP_KERNEL) allocates more memory
3. A subsequent error jumps to cifs_parse_mount_err
4. The old error handler freed passwords but not the source strings,
causing the memory to leak.&lt;/p&gt;
&lt;p&gt;This issue was not addressed by commit e8c73eb7db0a (&amp;#34;cifs: client:
fix memory leak in smb3_fs_context_parse_param&amp;#34;), which only fixed
leaks from repeated fsconfig() calls but not this error path.&lt;/p&gt;
&lt;p&gt;Patch updated with minor change suggested by kernel test robot&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-6qvg-p925-pxr9</guid>
    </item>
    <item>
      <title>msrc_CVE-2025-68219 — cifs: fix memory leak in smb3_fs_context_parse_param error path</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2025-68219</link>
      <description>msrc_CVE-2025-68219</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2025-68219</guid>
    </item>
    <item>
      <title>OESA-2026-1303 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2026-1303</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: 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;ptr_ring: do not block hard interrupts in ptr_ring_resize_multiple()&lt;/p&gt;
&lt;p&gt;Jakub added a lockdep_assert_no_hardirq() check in __page_pool_put_page()
to increase test coverage.&lt;/p&gt;
&lt;p&gt;syzbot found a splat caused by hard irq blocking in
ptr_ring_resize_multiple() [1]&lt;/p&gt;
&lt;p&gt;As current users of ptr_ring_resize_multiple() do not require
hard irqs being masked, replace it to only block BH.&lt;/p&gt;
&lt;p&gt;Rename helpers to better reflect they are safe against BH only.&lt;/p&gt;
&lt;p&gt;- ptr_ring_resize_multiple() to ptr_ring_resize_multiple_bh()
- skb_array_resize_multiple() to skb_array_resize_multiple_bh()&lt;/p&gt;
&lt;p&gt;[1]&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 1 PID: 9150 at net/core/page_pool.c:709 __page_pool_put_page net/core/page_pool.c:709 [inline]
WARNING: CPU: 1 PID: 9150 at net/core/page_pool.c:709 page_pool_put_unrefed_netmem+0x157/0xa40 net/core/page_pool.c:780
Modules linked in:
CPU: 1 UID: 0 PID: 9150 Comm: syz.1.1052 Not tainted 6.11.0-rc3-syzkaller-00202-gf8669d7b5f5d #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
RIP: 0010:__page_pool_put_page net/core/page_pool.c:709 [inline]
RIP: 0010:page_pool_put_unrefed_netmem+0x157/0xa40 net/core/page_pool.c:780
Code: 74 0e e8 7c aa fb f7 eb 43 e8 75 aa fb f7 eb 3c 65 8b 1d 38 a8 6a 76 31 ff 89 de e8 a3 ae fb f7 85 db 74 0b e8 5a aa fb f7 90 &amp;amp;lt;0f&amp;amp;gt; 0b 90 eb 1d 65 8b 1d 15 a8 6a 76 31 ff 89 de e8 84 ae fb f7 85
RSP:…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: 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;ptr_ring: do not block hard interrupts in ptr_ring_resize_multiple()&lt;/p&gt;
&lt;p&gt;Jakub added a lockdep_assert_no_hardirq() check in __page_pool_put_page()
to increase test coverage.&lt;/p&gt;
&lt;p&gt;syzbot found a splat caused by hard irq blocking in
ptr_ring_resize_multiple() [1]&lt;/p&gt;
&lt;p&gt;As current users of ptr_ring_resize_multiple() do not require
hard irqs being masked, replace it to only block BH.&lt;/p&gt;
&lt;p&gt;Rename helpers to better reflect they are safe against BH only.&lt;/p&gt;
&lt;p&gt;- ptr_ring_resize_multiple() to ptr_ring_resize_multiple_bh()
- skb_array_resize_multiple() to skb_array_resize_multiple_bh()&lt;/p&gt;
&lt;p&gt;[1]&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 1 PID: 9150 at net/core/page_pool.c:709 __page_pool_put_page net/core/page_pool.c:709 [inline]
WARNING: CPU: 1 PID: 9150 at net/core/page_pool.c:709 page_pool_put_unrefed_netmem+0x157/0xa40 net/core/page_pool.c:780
Modules linked in:
CPU: 1 UID: 0 PID: 9150 Comm: syz.1.1052 Not tainted 6.11.0-rc3-syzkaller-00202-gf8669d7b5f5d #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
RIP: 0010:__page_pool_put_page net/core/page_pool.c:709 [inline]
RIP: 0010:page_pool_put_unrefed_netmem+0x157/0xa40 net/core/page_pool.c:780
Code: 74 0e e8 7c aa fb f7 eb 43 e8 75 aa fb f7 eb 3c 65 8b 1d 38 a8 6a 76 31 ff 89 de e8 a3 ae fb f7 85 db 74 0b e8 5a aa fb f7 90 &amp;amp;lt;0f&amp;amp;gt; 0b 90 eb 1d 65 8b 1d 15 a8 6a 76 31 ff 89 de e8 84 ae fb f7 85
RSP:…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2026-1303</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-68219</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-68219</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 179 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: cifs: fix memory leak in smb3_fs_context_parse_param error path Add proper cleanup of ctx-&amp;gt;source and fc-&amp;gt;source to the cifs_parse_mount_err error handler. This ensures that memory allocated for the source strings is correctly freed on all error paths, matching the cleanup already performed in the success path by smb3_cleanup_fs_context_contents(). Pointers are also set to NULL after freeing to prevent potential double-free issues. This change fixes a memory leak originally detected by syzbot. The leak occurred when processing Opt_source mount options if an error happened after ctx-&amp;gt;source and fc-&amp;gt;source were successfully allocated but before the function completed. The specific leak sequence was: 1. ctx-&amp;gt;source = smb3_fs_context_fullpath(ctx, &amp;#39;/&amp;#39;) allocates memory 2. fc-&amp;gt;source = kstrdup(ctx-&amp;gt;source, GFP_KERNEL) allocates more memory 3. A subsequent error jumps to cifs_parse_mount_err 4. The old error handler freed passwords but not the source strings, causing the memory to leak. This issue was not addressed by commit e8c73eb7db0a (&amp;#34;cifs: client: fix memory leak in smb3_fs_context_parse_param&amp;#34;), which only fixed leaks from repeated fsconfig() calls but not this error path. Patch updated with minor change suggested by kernel test robot&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 179 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: cifs: fix memory leak in smb3_fs_context_parse_param error path Add proper cleanup of ctx-&amp;gt;source and fc-&amp;gt;source to the cifs_parse_mount_err error handler. This ensures that memory allocated for the source strings is correctly freed on all error paths, matching the cleanup already performed in the success path by smb3_cleanup_fs_context_contents(). Pointers are also set to NULL after freeing to prevent potential double-free issues. This change fixes a memory leak originally detected by syzbot. The leak occurred when processing Opt_source mount options if an error happened after ctx-&amp;gt;source and fc-&amp;gt;source were successfully allocated but before the function completed. The specific leak sequence was: 1. ctx-&amp;gt;source = smb3_fs_context_fullpath(ctx, &amp;#39;/&amp;#39;) allocates memory 2. fc-&amp;gt;source = kstrdup(ctx-&amp;gt;source, GFP_KERNEL) allocates more memory 3. A subsequent error jumps to cifs_parse_mount_err 4. The old error handler freed passwords but not the source strings, causing the memory to leak. This issue was not addressed by commit e8c73eb7db0a (&amp;#34;cifs: client: fix memory leak in smb3_fs_context_parse_param&amp;#34;), which only fixed leaks from repeated fsconfig() calls but not this error path. Patch updated with minor change suggested by kernel test robot&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-68219</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2868 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2868</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2868</guid>
    </item>
  </channel>
</rss>
