<?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://vulnerability.circl.lu</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 07:13:45 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-11841</title>
      <link>https://vulnerability.circl.lu/vuln/bdu:2026-11841</link>
      <description>bdu:2026-11841</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/bdu:2026-11841</guid>
    </item>
    <item>
      <title>BELL-CVE-2026-23297</title>
      <link>https://vulnerability.circl.lu/vuln/bell-cve-2026-23297</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/bell-cve-2026-23297</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0497 — 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://vulnerability.circl.lu/vuln/certfr-2026-avi-0497</link>
      <description>certfr-2026-avi-0497</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/certfr-2026-avi-0497</guid>
    </item>
    <item>
      <title>fkie_cve-2026-23297</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-23297</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;nfsd: Fix cred ref leak in nfsd_nl_threads_set_doit().&lt;/p&gt;
&lt;p&gt;syzbot reported memory leak of struct cred. [0]&lt;/p&gt;
&lt;p&gt;nfsd_nl_threads_set_doit() passes get_current_cred() to
nfsd_svc(), but put_cred() is not called after that.&lt;/p&gt;
&lt;p&gt;The cred is finally passed down to _svc_xprt_create(),
which calls get_cred() with the cred for struct svc_xprt.&lt;/p&gt;
&lt;p&gt;The ownership of the refcount by get_current_cred() is not
transferred to anywhere and is just leaked.&lt;/p&gt;
&lt;p&gt;nfsd_svc() is also called from write_threads(), but it does
not bump file-&amp;gt;f_cred there.&lt;/p&gt;
&lt;p&gt;nfsd_nl_threads_set_doit() is called from sendmsg() and
current-&amp;gt;cred does not go away.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s use current_cred() in nfsd_nl_threads_set_doit().&lt;/p&gt;
&lt;p&gt;[0]:
BUG: memory leak
unreferenced object 0xffff888108b89480 (size 184):
  comm &amp;#34;syz-executor&amp;#34;, pid 5994, jiffies 4294943386
  hex dump (first 32 bytes):
    01 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 (crc 369454a7):
    kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
    slab_post_alloc_hook mm/slub.c:4958 [inline]
    slab_alloc_node mm/slub.c:5263 [inline]
    kmem_cache_alloc_noprof+0x412/0x580 mm/slub.c:5270
    prepare_creds+0x22/0x600 kernel/cred.c:185
    copy_creds+0x44/0x290 kernel/cred.c:286
    copy_process+0x7a7/0x2870 kernel/fork.c:2086
    kernel_clone+0xac/0x6e0 kernel/fork.c:2651
    __do_sys_clone+0x7f/0xb0 kernel/fo…&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;nfsd: Fix cred ref leak in nfsd_nl_threads_set_doit().&lt;/p&gt;
&lt;p&gt;syzbot reported memory leak of struct cred. [0]&lt;/p&gt;
&lt;p&gt;nfsd_nl_threads_set_doit() passes get_current_cred() to
nfsd_svc(), but put_cred() is not called after that.&lt;/p&gt;
&lt;p&gt;The cred is finally passed down to _svc_xprt_create(),
which calls get_cred() with the cred for struct svc_xprt.&lt;/p&gt;
&lt;p&gt;The ownership of the refcount by get_current_cred() is not
transferred to anywhere and is just leaked.&lt;/p&gt;
&lt;p&gt;nfsd_svc() is also called from write_threads(), but it does
not bump file-&amp;gt;f_cred there.&lt;/p&gt;
&lt;p&gt;nfsd_nl_threads_set_doit() is called from sendmsg() and
current-&amp;gt;cred does not go away.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s use current_cred() in nfsd_nl_threads_set_doit().&lt;/p&gt;
&lt;p&gt;[0]:
BUG: memory leak
unreferenced object 0xffff888108b89480 (size 184):
  comm &amp;#34;syz-executor&amp;#34;, pid 5994, jiffies 4294943386
  hex dump (first 32 bytes):
    01 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 (crc 369454a7):
    kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
    slab_post_alloc_hook mm/slub.c:4958 [inline]
    slab_alloc_node mm/slub.c:5263 [inline]
    kmem_cache_alloc_noprof+0x412/0x580 mm/slub.c:5270
    prepare_creds+0x22/0x600 kernel/cred.c:185
    copy_creds+0x44/0x290 kernel/cred.c:286
    copy_process+0x7a7/0x2870 kernel/fork.c:2086
    kernel_clone+0xac/0x6e0 kernel/fork.c:2651
    __do_sys_clone+0x7f/0xb0 kernel/fo…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-23297</guid>
    </item>
    <item>
      <title>GHSA-pxcg-3rj5-5gx5</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-pxcg-3rj5-5gx5</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;nfsd: Fix cred ref leak in nfsd_nl_threads_set_doit().&lt;/p&gt;
&lt;p&gt;syzbot reported memory leak of struct cred. [0]&lt;/p&gt;
&lt;p&gt;nfsd_nl_threads_set_doit() passes get_current_cred() to
nfsd_svc(), but put_cred() is not called after that.&lt;/p&gt;
&lt;p&gt;The cred is finally passed down to _svc_xprt_create(),
which calls get_cred() with the cred for struct svc_xprt.&lt;/p&gt;
&lt;p&gt;The ownership of the refcount by get_current_cred() is not
transferred to anywhere and is just leaked.&lt;/p&gt;
&lt;p&gt;nfsd_svc() is also called from write_threads(), but it does
not bump file-&amp;gt;f_cred there.&lt;/p&gt;
&lt;p&gt;nfsd_nl_threads_set_doit() is called from sendmsg() and
current-&amp;gt;cred does not go away.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s use current_cred() in nfsd_nl_threads_set_doit().&lt;/p&gt;
&lt;p&gt;[0]:
BUG: memory leak
unreferenced object 0xffff888108b89480 (size 184):
  comm &amp;#34;syz-executor&amp;#34;, pid 5994, jiffies 4294943386
  hex dump (first 32 bytes):
    01 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 (crc 369454a7):
    kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
    slab_post_alloc_hook mm/slub.c:4958 [inline]
    slab_alloc_node mm/slub.c:5263 [inline]
    kmem_cache_alloc_noprof+0x412/0x580 mm/slub.c:5270
    prepare_creds+0x22/0x600 kernel/cred.c:185
    copy_creds+0x44/0x290 kernel/cred.c:286
    copy_process+0x7a7/0x2870 kernel/fork.c:2086
    kernel_clone+0xac/0x6e0 kernel/fork.c:2651
    __do_sys_clone+0x7f/0xb0 kernel/fo…&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;nfsd: Fix cred ref leak in nfsd_nl_threads_set_doit().&lt;/p&gt;
&lt;p&gt;syzbot reported memory leak of struct cred. [0]&lt;/p&gt;
&lt;p&gt;nfsd_nl_threads_set_doit() passes get_current_cred() to
nfsd_svc(), but put_cred() is not called after that.&lt;/p&gt;
&lt;p&gt;The cred is finally passed down to _svc_xprt_create(),
which calls get_cred() with the cred for struct svc_xprt.&lt;/p&gt;
&lt;p&gt;The ownership of the refcount by get_current_cred() is not
transferred to anywhere and is just leaked.&lt;/p&gt;
&lt;p&gt;nfsd_svc() is also called from write_threads(), but it does
not bump file-&amp;gt;f_cred there.&lt;/p&gt;
&lt;p&gt;nfsd_nl_threads_set_doit() is called from sendmsg() and
current-&amp;gt;cred does not go away.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s use current_cred() in nfsd_nl_threads_set_doit().&lt;/p&gt;
&lt;p&gt;[0]:
BUG: memory leak
unreferenced object 0xffff888108b89480 (size 184):
  comm &amp;#34;syz-executor&amp;#34;, pid 5994, jiffies 4294943386
  hex dump (first 32 bytes):
    01 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 (crc 369454a7):
    kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
    slab_post_alloc_hook mm/slub.c:4958 [inline]
    slab_alloc_node mm/slub.c:5263 [inline]
    kmem_cache_alloc_noprof+0x412/0x580 mm/slub.c:5270
    prepare_creds+0x22/0x600 kernel/cred.c:185
    copy_creds+0x44/0x290 kernel/cred.c:286
    copy_process+0x7a7/0x2870 kernel/fork.c:2086
    kernel_clone+0xac/0x6e0 kernel/fork.c:2651
    __do_sys_clone+0x7f/0xb0 kernel/fo…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-pxcg-3rj5-5gx5</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:20572-1 — Security update for the Linux Kernel</title>
      <link>https://vulnerability.circl.lu/vuln/opensuse-su-2026:20572-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://vulnerability.circl.lu/vuln/opensuse-su-2026:20572-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:21230-1 — Security update for the Linux Kernel</title>
      <link>https://vulnerability.circl.lu/vuln/suse-su-2026:21230-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://vulnerability.circl.lu/vuln/suse-su-2026:21230-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-23297</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-23297</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 106 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: nfsd: Fix cred ref leak in nfsd_nl_threads_set_doit(). syzbot reported memory leak of struct cred. [0] nfsd_nl_threads_set_doit() passes get_current_cred() to nfsd_svc(), but put_cred() is not called after that. The cred is finally passed down to _svc_xprt_create(), which calls get_cred() with the cred for struct svc_xprt. The ownership of the refcount by get_current_cred() is not transferred to anywhere and is just leaked. nfsd_svc() is also called from write_threads(), but it does not bump file-&amp;gt;f_cred there. nfsd_nl_threads_set_doit() is called from sendmsg() and current-&amp;gt;cred does not go away. Let&amp;#39;s use current_cred() in nfsd_nl_threads_set_doit(). [0]: BUG: memory leak unreferenced object 0xffff888108b89480 (size 184):   comm &amp;#34;syz-executor&amp;#34;, pid 5994, jiffies 4294943386   hex dump (first 32 bytes):     01 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 (crc 369454a7):     kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]     slab_post_alloc_hook mm/slub.c:4958 [inline]     slab_alloc_node mm/slub.c:5263 [inline]     kmem_cache_alloc_noprof+0x412/0x580 mm/slub.c:5270     prepare_creds+0x22/0x600 kernel/cred.c:185     copy_creds+0x44/0x290 kernel/cred.c:286     copy_process+0x7a7/0x2870 kernel/fork.c:2086     kernel_clone+0xac/0x6e0 kernel/fork.c:2651     __do_sys_clone+0x7f/0xb0 kernel/fork.c:2792…&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 106 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: nfsd: Fix cred ref leak in nfsd_nl_threads_set_doit(). syzbot reported memory leak of struct cred. [0] nfsd_nl_threads_set_doit() passes get_current_cred() to nfsd_svc(), but put_cred() is not called after that. The cred is finally passed down to _svc_xprt_create(), which calls get_cred() with the cred for struct svc_xprt. The ownership of the refcount by get_current_cred() is not transferred to anywhere and is just leaked. nfsd_svc() is also called from write_threads(), but it does not bump file-&amp;gt;f_cred there. nfsd_nl_threads_set_doit() is called from sendmsg() and current-&amp;gt;cred does not go away. Let&amp;#39;s use current_cred() in nfsd_nl_threads_set_doit(). [0]: BUG: memory leak unreferenced object 0xffff888108b89480 (size 184):   comm &amp;#34;syz-executor&amp;#34;, pid 5994, jiffies 4294943386   hex dump (first 32 bytes):     01 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 (crc 369454a7):     kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]     slab_post_alloc_hook mm/slub.c:4958 [inline]     slab_alloc_node mm/slub.c:5263 [inline]     kmem_cache_alloc_noprof+0x412/0x580 mm/slub.c:5270     prepare_creds+0x22/0x600 kernel/cred.c:185     copy_creds+0x44/0x290 kernel/cred.c:286     copy_process+0x7a7/0x2870 kernel/fork.c:2086     kernel_clone+0xac/0x6e0 kernel/fork.c:2651     __do_sys_clone+0x7f/0xb0 kernel/fork.c:2792…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-23297</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-0861 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://vulnerability.circl.lu/vuln/wid-sec-w-2026-0861</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service zu verursachen, Sicherheitsmaßnahmen zu umgehen, Informationen offenzulegen, weitere nicht spezifizierte Auswirkungen zu verursachen und potentiell Code auszuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service zu verursachen, Sicherheitsmaßnahmen zu umgehen, Informationen offenzulegen, weitere nicht spezifizierte Auswirkungen zu verursachen und potentiell Code auszuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/wid-sec-w-2026-0861</guid>
    </item>
  </channel>
</rss>
