<?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>Sat, 03 Oct 2026 08:52:24 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-72468</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-72468</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://cve.radiocsirt.org/vuln/bell-cve-2026-72468</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1255 — 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-2026-avi-1255</link>
      <description>certfr-2026-avi-1255</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1255</guid>
    </item>
    <item>
      <title>EUVD-2026-353788</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-353788</link>
      <description>EUVD-2026-353788</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-353788</guid>
    </item>
    <item>
      <title>fkie_cve-2026-72468</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-72468</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;xprtrdma: Initialize re_id before removal registration&lt;/p&gt;
&lt;p&gt;rpcrdma_create_id() registers ep-&amp;gt;re_rn with the rpcrdma ib_client
before returning the new rdma_cm_id to rpcrdma_ep_create(). However
rpcrdma_ep_create() currently stores that pointer in ep-&amp;gt;re_id only
after rpcrdma_create_id() returns.&lt;/p&gt;
&lt;p&gt;A local administrator can race an NFS/RDMA mount against RDMA device
removal. If rpcrdma_remove_one() observes the just-registered
notification before rpcrdma_ep_create() assigns ep-&amp;gt;re_id,
rpcrdma_ep_removal_done() calls trace_xprtrdma_device_removal(NULL).
The tracepoint dereferences id-&amp;gt;device-&amp;gt;name and copies
id-&amp;gt;route.addr.dst_addr, so the callback can crash the kernel with a
NULL pointer dereference.&lt;/p&gt;
&lt;p&gt;Store the rdma_cm_id in ep-&amp;gt;re_id immediately before publishing
ep-&amp;gt;re_rn. The existing error path still destroys the id directly if
registration fails; ep is then freed by the caller without using
ep-&amp;gt;re_id. Remove the later duplicate assignment in rpcrdma_ep_create().&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;xprtrdma: Initialize re_id before removal registration&lt;/p&gt;
&lt;p&gt;rpcrdma_create_id() registers ep-&amp;gt;re_rn with the rpcrdma ib_client
before returning the new rdma_cm_id to rpcrdma_ep_create(). However
rpcrdma_ep_create() currently stores that pointer in ep-&amp;gt;re_id only
after rpcrdma_create_id() returns.&lt;/p&gt;
&lt;p&gt;A local administrator can race an NFS/RDMA mount against RDMA device
removal. If rpcrdma_remove_one() observes the just-registered
notification before rpcrdma_ep_create() assigns ep-&amp;gt;re_id,
rpcrdma_ep_removal_done() calls trace_xprtrdma_device_removal(NULL).
The tracepoint dereferences id-&amp;gt;device-&amp;gt;name and copies
id-&amp;gt;route.addr.dst_addr, so the callback can crash the kernel with a
NULL pointer dereference.&lt;/p&gt;
&lt;p&gt;Store the rdma_cm_id in ep-&amp;gt;re_id immediately before publishing
ep-&amp;gt;re_rn. The existing error path still destroys the id directly if
registration fails; ep is then freed by the caller without using
ep-&amp;gt;re_id. Remove the later duplicate assignment in rpcrdma_ep_create().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-72468</guid>
    </item>
    <item>
      <title>GHSA-5xgh-rmhf-2qq8</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-5xgh-rmhf-2qq8</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;xprtrdma: Initialize re_id before removal registration&lt;/p&gt;
&lt;p&gt;rpcrdma_create_id() registers ep-&amp;gt;re_rn with the rpcrdma ib_client
before returning the new rdma_cm_id to rpcrdma_ep_create(). However
rpcrdma_ep_create() currently stores that pointer in ep-&amp;gt;re_id only
after rpcrdma_create_id() returns.&lt;/p&gt;
&lt;p&gt;A local administrator can race an NFS/RDMA mount against RDMA device
removal. If rpcrdma_remove_one() observes the just-registered
notification before rpcrdma_ep_create() assigns ep-&amp;gt;re_id,
rpcrdma_ep_removal_done() calls trace_xprtrdma_device_removal(NULL).
The tracepoint dereferences id-&amp;gt;device-&amp;gt;name and copies
id-&amp;gt;route.addr.dst_addr, so the callback can crash the kernel with a
NULL pointer dereference.&lt;/p&gt;
&lt;p&gt;Store the rdma_cm_id in ep-&amp;gt;re_id immediately before publishing
ep-&amp;gt;re_rn. The existing error path still destroys the id directly if
registration fails; ep is then freed by the caller without using
ep-&amp;gt;re_id. Remove the later duplicate assignment in rpcrdma_ep_create().&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;xprtrdma: Initialize re_id before removal registration&lt;/p&gt;
&lt;p&gt;rpcrdma_create_id() registers ep-&amp;gt;re_rn with the rpcrdma ib_client
before returning the new rdma_cm_id to rpcrdma_ep_create(). However
rpcrdma_ep_create() currently stores that pointer in ep-&amp;gt;re_id only
after rpcrdma_create_id() returns.&lt;/p&gt;
&lt;p&gt;A local administrator can race an NFS/RDMA mount against RDMA device
removal. If rpcrdma_remove_one() observes the just-registered
notification before rpcrdma_ep_create() assigns ep-&amp;gt;re_id,
rpcrdma_ep_removal_done() calls trace_xprtrdma_device_removal(NULL).
The tracepoint dereferences id-&amp;gt;device-&amp;gt;name and copies
id-&amp;gt;route.addr.dst_addr, so the callback can crash the kernel with a
NULL pointer dereference.&lt;/p&gt;
&lt;p&gt;Store the rdma_cm_id in ep-&amp;gt;re_id immediately before publishing
ep-&amp;gt;re_rn. The existing error path still destroys the id directly if
registration fails; ep is then freed by the caller without using
ep-&amp;gt;re_id. Remove the later duplicate assignment in rpcrdma_ep_create().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-5xgh-rmhf-2qq8</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:21910-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/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://cve.radiocsirt.org/vuln/opensuse-su-2026:21910-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:23881-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/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://cve.radiocsirt.org/vuln/suse-su-2026:23881-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-72468</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-72468</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 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: xprtrdma: Initialize re_id before removal registration rpcrdma_create_id() registers ep-&amp;gt;re_rn with the rpcrdma ib_client before returning the new rdma_cm_id to rpcrdma_ep_create(). However rpcrdma_ep_create() currently stores that pointer in ep-&amp;gt;re_id only after rpcrdma_create_id() returns. A local administrator can race an NFS/RDMA mount against RDMA device removal. If rpcrdma_remove_one() observes the just-registered notification before rpcrdma_ep_create() assigns ep-&amp;gt;re_id, rpcrdma_ep_removal_done() calls trace_xprtrdma_device_removal(NULL). The tracepoint dereferences id-&amp;gt;device-&amp;gt;name and copies id-&amp;gt;route.addr.dst_addr, so the callback can crash the kernel with a NULL pointer dereference. Store the rdma_cm_id in ep-&amp;gt;re_id immediately before publishing ep-&amp;gt;re_rn. The existing error path still destroys the id directly if registration fails; ep is then freed by the caller without using ep-&amp;gt;re_id. Remove the later duplicate assignment in rpcrdma_ep_create().&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 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: xprtrdma: Initialize re_id before removal registration rpcrdma_create_id() registers ep-&amp;gt;re_rn with the rpcrdma ib_client before returning the new rdma_cm_id to rpcrdma_ep_create(). However rpcrdma_ep_create() currently stores that pointer in ep-&amp;gt;re_id only after rpcrdma_create_id() returns. A local administrator can race an NFS/RDMA mount against RDMA device removal. If rpcrdma_remove_one() observes the just-registered notification before rpcrdma_ep_create() assigns ep-&amp;gt;re_id, rpcrdma_ep_removal_done() calls trace_xprtrdma_device_removal(NULL). The tracepoint dereferences id-&amp;gt;device-&amp;gt;name and copies id-&amp;gt;route.addr.dst_addr, so the callback can crash the kernel with a NULL pointer dereference. Store the rdma_cm_id in ep-&amp;gt;re_id immediately before publishing ep-&amp;gt;re_rn. The existing error path still destroys the id directly if registration fails; ep is then freed by the caller without using ep-&amp;gt;re_id. Remove the later duplicate assignment in rpcrdma_ep_create().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-72468</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2852 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852</guid>
    </item>
  </channel>
</rss>
