<?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>Fri, 02 Oct 2026 15:07:17 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-64033</title>
      <link>https://vulnerability.circl.lu/vuln/bell-cve-2026-64033</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://vulnerability.circl.lu/vuln/bell-cve-2026-64033</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0926 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://vulnerability.circl.lu/vuln/certfr-2026-avi-0926</link>
      <description>certfr-2026-avi-0926</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/certfr-2026-avi-0926</guid>
    </item>
    <item>
      <title>fkie_cve-2026-64033</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-64033</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;RDMA/rtrs: Fix use-after-free in path file creation cleanup&lt;/p&gt;
&lt;p&gt;In the error path of rtrs_srv_create_path_files(), the sysfs root folders
may already have been created and srv_path-&amp;gt;kobj may already have been
initialized. If a later step fails, the cleanup currently calls
kobject_put(&amp;amp;srv_path-&amp;gt;kobj) before
rtrs_srv_destroy_once_sysfs_root_folders(srv_path).&lt;/p&gt;
&lt;p&gt;kobject_put() may drop the last reference to srv_path-&amp;gt;kobj and invoke the
release callback, rtrs_srv_release(), which frees srv_path. The following
call to rtrs_srv_destroy_once_sysfs_root_folders(srv_path) then
dereferences srv_path internally to access srv_path-&amp;gt;srv, resulting in a
use-after-free.&lt;/p&gt;
&lt;p&gt;This failure path is reached before rtrs_srv_create_path_files() returns
success, so the successful-path lifetime handling is not involved.&lt;/p&gt;
&lt;p&gt;Fix this by destroying the sysfs root folders before calling
kobject_put(&amp;amp;srv_path-&amp;gt;kobj), so srv_path is still valid while the helper
accesses it.&lt;/p&gt;
&lt;p&gt;This issue was found by a static analysis tool I am developing.&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;RDMA/rtrs: Fix use-after-free in path file creation cleanup&lt;/p&gt;
&lt;p&gt;In the error path of rtrs_srv_create_path_files(), the sysfs root folders
may already have been created and srv_path-&amp;gt;kobj may already have been
initialized. If a later step fails, the cleanup currently calls
kobject_put(&amp;amp;srv_path-&amp;gt;kobj) before
rtrs_srv_destroy_once_sysfs_root_folders(srv_path).&lt;/p&gt;
&lt;p&gt;kobject_put() may drop the last reference to srv_path-&amp;gt;kobj and invoke the
release callback, rtrs_srv_release(), which frees srv_path. The following
call to rtrs_srv_destroy_once_sysfs_root_folders(srv_path) then
dereferences srv_path internally to access srv_path-&amp;gt;srv, resulting in a
use-after-free.&lt;/p&gt;
&lt;p&gt;This failure path is reached before rtrs_srv_create_path_files() returns
success, so the successful-path lifetime handling is not involved.&lt;/p&gt;
&lt;p&gt;Fix this by destroying the sysfs root folders before calling
kobject_put(&amp;amp;srv_path-&amp;gt;kobj), so srv_path is still valid while the helper
accesses it.&lt;/p&gt;
&lt;p&gt;This issue was found by a static analysis tool I am developing.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-64033</guid>
    </item>
    <item>
      <title>GHSA-2qpc-f6fh-fxg4</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-2qpc-f6fh-fxg4</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;RDMA/rtrs: Fix use-after-free in path file creation cleanup&lt;/p&gt;
&lt;p&gt;In the error path of rtrs_srv_create_path_files(), the sysfs root folders
may already have been created and srv_path-&amp;gt;kobj may already have been
initialized. If a later step fails, the cleanup currently calls
kobject_put(&amp;amp;srv_path-&amp;gt;kobj) before
rtrs_srv_destroy_once_sysfs_root_folders(srv_path).&lt;/p&gt;
&lt;p&gt;kobject_put() may drop the last reference to srv_path-&amp;gt;kobj and invoke the
release callback, rtrs_srv_release(), which frees srv_path. The following
call to rtrs_srv_destroy_once_sysfs_root_folders(srv_path) then
dereferences srv_path internally to access srv_path-&amp;gt;srv, resulting in a
use-after-free.&lt;/p&gt;
&lt;p&gt;This failure path is reached before rtrs_srv_create_path_files() returns
success, so the successful-path lifetime handling is not involved.&lt;/p&gt;
&lt;p&gt;Fix this by destroying the sysfs root folders before calling
kobject_put(&amp;amp;srv_path-&amp;gt;kobj), so srv_path is still valid while the helper
accesses it.&lt;/p&gt;
&lt;p&gt;This issue was found by a static analysis tool I am developing.&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;RDMA/rtrs: Fix use-after-free in path file creation cleanup&lt;/p&gt;
&lt;p&gt;In the error path of rtrs_srv_create_path_files(), the sysfs root folders
may already have been created and srv_path-&amp;gt;kobj may already have been
initialized. If a later step fails, the cleanup currently calls
kobject_put(&amp;amp;srv_path-&amp;gt;kobj) before
rtrs_srv_destroy_once_sysfs_root_folders(srv_path).&lt;/p&gt;
&lt;p&gt;kobject_put() may drop the last reference to srv_path-&amp;gt;kobj and invoke the
release callback, rtrs_srv_release(), which frees srv_path. The following
call to rtrs_srv_destroy_once_sysfs_root_folders(srv_path) then
dereferences srv_path internally to access srv_path-&amp;gt;srv, resulting in a
use-after-free.&lt;/p&gt;
&lt;p&gt;This failure path is reached before rtrs_srv_create_path_files() returns
success, so the successful-path lifetime handling is not involved.&lt;/p&gt;
&lt;p&gt;Fix this by destroying the sysfs root folders before calling
kobject_put(&amp;amp;srv_path-&amp;gt;kobj), so srv_path is still valid while the helper
accesses it.&lt;/p&gt;
&lt;p&gt;This issue was found by a static analysis tool I am developing.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-2qpc-f6fh-fxg4</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:21910-1 — Security update for the Linux Kernel</title>
      <link>https://vulnerability.circl.lu/vuln/opensuse-su-2026:21910-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:21910-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:23881-1 — Security update for the Linux Kernel</title>
      <link>https://vulnerability.circl.lu/vuln/suse-su-2026:23881-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:23881-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-64033</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-64033</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 192 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: RDMA/rtrs: Fix use-after-free in path file creation cleanup In the error path of rtrs_srv_create_path_files(), the sysfs root folders may already have been created and srv_path-&amp;gt;kobj may already have been initialized. If a later step fails, the cleanup currently calls kobject_put(&amp;amp;srv_path-&amp;gt;kobj) before rtrs_srv_destroy_once_sysfs_root_folders(srv_path). kobject_put() may drop the last reference to srv_path-&amp;gt;kobj and invoke the release callback, rtrs_srv_release(), which frees srv_path. The following call to rtrs_srv_destroy_once_sysfs_root_folders(srv_path) then dereferences srv_path internally to access srv_path-&amp;gt;srv, resulting in a use-after-free. This failure path is reached before rtrs_srv_create_path_files() returns success, so the successful-path lifetime handling is not involved. Fix this by destroying the sysfs root folders before calling kobject_put(&amp;amp;srv_path-&amp;gt;kobj), so srv_path is still valid while the helper accesses it. This issue was found by a static analysis tool I am developing.&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 192 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: RDMA/rtrs: Fix use-after-free in path file creation cleanup In the error path of rtrs_srv_create_path_files(), the sysfs root folders may already have been created and srv_path-&amp;gt;kobj may already have been initialized. If a later step fails, the cleanup currently calls kobject_put(&amp;amp;srv_path-&amp;gt;kobj) before rtrs_srv_destroy_once_sysfs_root_folders(srv_path). kobject_put() may drop the last reference to srv_path-&amp;gt;kobj and invoke the release callback, rtrs_srv_release(), which frees srv_path. The following call to rtrs_srv_destroy_once_sysfs_root_folders(srv_path) then dereferences srv_path internally to access srv_path-&amp;gt;srv, resulting in a use-after-free. This failure path is reached before rtrs_srv_create_path_files() returns success, so the successful-path lifetime handling is not involved. Fix this by destroying the sysfs root folders before calling kobject_put(&amp;amp;srv_path-&amp;gt;kobj), so srv_path is still valid while the helper accesses it. This issue was found by a static analysis tool I am developing.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-64033</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2403 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://vulnerability.circl.lu/vuln/wid-sec-w-2026-2403</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/wid-sec-w-2026-2403</guid>
    </item>
  </channel>
</rss>
