<?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 14:23:25 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-72469</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-72469</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-2026-72469</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1164 — 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-1164</link>
      <description>certfr-2026-avi-1164</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1164</guid>
    </item>
    <item>
      <title>EUVD-2026-354113</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-354113</link>
      <description>EUVD-2026-354113</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-354113</guid>
    </item>
    <item>
      <title>fkie_cve-2026-72469</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-72469</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;xprtrdma: Fix ep kref imbalance on ADDR_CHANGE&lt;/p&gt;
&lt;p&gt;rpcrdma_cm_event_handler() falls through to the disconnected: label
on RDMA_CM_EVENT_ADDR_CHANGE and calls rpcrdma_ep_put() with no
matching get when the event arrives before RDMA_CM_EVENT_ESTABLISHED.
The kref then underflows during connect teardown and
rpcrdma_xprt_disconnect() operates on a freed ep.&lt;/p&gt;
&lt;p&gt;Reference counts across a normal connection lifecycle:&lt;/p&gt;
&lt;p&gt;rpcrdma_ep_create()             kref_init     -&amp;gt;1
    rpcrdma_xprt_connect()          ep_get        -&amp;gt;2  (before post_recvs)
    RDMA_CM_EVENT_ESTABLISHED       ep_get        -&amp;gt;3
    RDMA_CM_EVENT_DISCONNECTED      ep_put        -&amp;gt;2
    rpcrdma_xprt_drain()            ep_put        -&amp;gt;1
    rpcrdma_xprt_disconnect() tail  ep_put        -&amp;gt;0  (ep_destroy)&lt;/p&gt;
&lt;p&gt;The connect-time get in rpcrdma_xprt_connect(), taken just before
rpcrdma_post_recvs() &amp;#34;while there are outstanding Receives,&amp;#34; is
balanced by rpcrdma_xprt_drain. ADDR_CHANGE before ESTABLISHED has
no get to consume, so its put drops the count to 1 and the drain
put then frees the ep while rpcrdma_xprt_disconnect() still holds a
pointer to it.&lt;/p&gt;
&lt;p&gt;Fix by dispatching on the prior re_connect_status via xchg(): for
prev == 0 (pre-ESTABLISHED) wake the connect waiter and return with
no put; for prev == 1 call rpcrdma_force_disconnect() and return.
The case-1 arm relies on the subsequent RDMA_CM_EVENT_DISCONNECTED
event -- reliably delivered when rdma_disconnec…&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: Fix ep kref imbalance on ADDR_CHANGE&lt;/p&gt;
&lt;p&gt;rpcrdma_cm_event_handler() falls through to the disconnected: label
on RDMA_CM_EVENT_ADDR_CHANGE and calls rpcrdma_ep_put() with no
matching get when the event arrives before RDMA_CM_EVENT_ESTABLISHED.
The kref then underflows during connect teardown and
rpcrdma_xprt_disconnect() operates on a freed ep.&lt;/p&gt;
&lt;p&gt;Reference counts across a normal connection lifecycle:&lt;/p&gt;
&lt;p&gt;rpcrdma_ep_create()             kref_init     -&amp;gt;1
    rpcrdma_xprt_connect()          ep_get        -&amp;gt;2  (before post_recvs)
    RDMA_CM_EVENT_ESTABLISHED       ep_get        -&amp;gt;3
    RDMA_CM_EVENT_DISCONNECTED      ep_put        -&amp;gt;2
    rpcrdma_xprt_drain()            ep_put        -&amp;gt;1
    rpcrdma_xprt_disconnect() tail  ep_put        -&amp;gt;0  (ep_destroy)&lt;/p&gt;
&lt;p&gt;The connect-time get in rpcrdma_xprt_connect(), taken just before
rpcrdma_post_recvs() &amp;#34;while there are outstanding Receives,&amp;#34; is
balanced by rpcrdma_xprt_drain. ADDR_CHANGE before ESTABLISHED has
no get to consume, so its put drops the count to 1 and the drain
put then frees the ep while rpcrdma_xprt_disconnect() still holds a
pointer to it.&lt;/p&gt;
&lt;p&gt;Fix by dispatching on the prior re_connect_status via xchg(): for
prev == 0 (pre-ESTABLISHED) wake the connect waiter and return with
no put; for prev == 1 call rpcrdma_force_disconnect() and return.
The case-1 arm relies on the subsequent RDMA_CM_EVENT_DISCONNECTED
event -- reliably delivered when rdma_disconnec…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-72469</guid>
    </item>
    <item>
      <title>GHSA-w6wr-jw44-5f3c</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-w6wr-jw44-5f3c</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;xprtrdma: Fix ep kref imbalance on ADDR_CHANGE&lt;/p&gt;
&lt;p&gt;rpcrdma_cm_event_handler() falls through to the disconnected: label
on RDMA_CM_EVENT_ADDR_CHANGE and calls rpcrdma_ep_put() with no
matching get when the event arrives before RDMA_CM_EVENT_ESTABLISHED.
The kref then underflows during connect teardown and
rpcrdma_xprt_disconnect() operates on a freed ep.&lt;/p&gt;
&lt;p&gt;Reference counts across a normal connection lifecycle:&lt;/p&gt;
&lt;p&gt;rpcrdma_ep_create()             kref_init     -&amp;gt;1
    rpcrdma_xprt_connect()          ep_get        -&amp;gt;2  (before post_recvs)
    RDMA_CM_EVENT_ESTABLISHED       ep_get        -&amp;gt;3
    RDMA_CM_EVENT_DISCONNECTED      ep_put        -&amp;gt;2
    rpcrdma_xprt_drain()            ep_put        -&amp;gt;1
    rpcrdma_xprt_disconnect() tail  ep_put        -&amp;gt;0  (ep_destroy)&lt;/p&gt;
&lt;p&gt;The connect-time get in rpcrdma_xprt_connect(), taken just before
rpcrdma_post_recvs() &amp;#34;while there are outstanding Receives,&amp;#34; is
balanced by rpcrdma_xprt_drain. ADDR_CHANGE before ESTABLISHED has
no get to consume, so its put drops the count to 1 and the drain
put then frees the ep while rpcrdma_xprt_disconnect() still holds a
pointer to it.&lt;/p&gt;
&lt;p&gt;Fix by dispatching on the prior re_connect_status via xchg(): for
prev == 0 (pre-ESTABLISHED) wake the connect waiter and return with
no put; for prev == 1 call rpcrdma_force_disconnect() and return.
The case-1 arm relies on the subsequent RDMA_CM_EVENT_DISCONNECTED
event -- reliably delivered when rdma_disconnec…&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: Fix ep kref imbalance on ADDR_CHANGE&lt;/p&gt;
&lt;p&gt;rpcrdma_cm_event_handler() falls through to the disconnected: label
on RDMA_CM_EVENT_ADDR_CHANGE and calls rpcrdma_ep_put() with no
matching get when the event arrives before RDMA_CM_EVENT_ESTABLISHED.
The kref then underflows during connect teardown and
rpcrdma_xprt_disconnect() operates on a freed ep.&lt;/p&gt;
&lt;p&gt;Reference counts across a normal connection lifecycle:&lt;/p&gt;
&lt;p&gt;rpcrdma_ep_create()             kref_init     -&amp;gt;1
    rpcrdma_xprt_connect()          ep_get        -&amp;gt;2  (before post_recvs)
    RDMA_CM_EVENT_ESTABLISHED       ep_get        -&amp;gt;3
    RDMA_CM_EVENT_DISCONNECTED      ep_put        -&amp;gt;2
    rpcrdma_xprt_drain()            ep_put        -&amp;gt;1
    rpcrdma_xprt_disconnect() tail  ep_put        -&amp;gt;0  (ep_destroy)&lt;/p&gt;
&lt;p&gt;The connect-time get in rpcrdma_xprt_connect(), taken just before
rpcrdma_post_recvs() &amp;#34;while there are outstanding Receives,&amp;#34; is
balanced by rpcrdma_xprt_drain. ADDR_CHANGE before ESTABLISHED has
no get to consume, so its put drops the count to 1 and the drain
put then frees the ep while rpcrdma_xprt_disconnect() still holds a
pointer to it.&lt;/p&gt;
&lt;p&gt;Fix by dispatching on the prior re_connect_status via xchg(): for
prev == 0 (pre-ESTABLISHED) wake the connect waiter and return with
no put; for prev == 1 call rpcrdma_force_disconnect() and return.
The case-1 arm relies on the subsequent RDMA_CM_EVENT_DISCONNECTED
event -- reliably delivered when rdma_disconnec…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-w6wr-jw44-5f3c</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-72469 — xprtrdma: Fix ep kref imbalance on ADDR_CHANGE</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-72469</link>
      <description>msrc_CVE-2026-72469</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-72469</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:23477-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:23477-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:23477-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-72469</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-72469</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 193 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: xprtrdma: Fix ep kref imbalance on ADDR_CHANGE rpcrdma_cm_event_handler() falls through to the disconnected: label on RDMA_CM_EVENT_ADDR_CHANGE and calls rpcrdma_ep_put() with no matching get when the event arrives before RDMA_CM_EVENT_ESTABLISHED. The kref then underflows during connect teardown and rpcrdma_xprt_disconnect() operates on a freed ep. Reference counts across a normal connection lifecycle:     rpcrdma_ep_create()             kref_init     -&amp;gt;1     rpcrdma_xprt_connect()          ep_get        -&amp;gt;2  (before post_recvs)     RDMA_CM_EVENT_ESTABLISHED       ep_get        -&amp;gt;3     RDMA_CM_EVENT_DISCONNECTED      ep_put        -&amp;gt;2     rpcrdma_xprt_drain()            ep_put        -&amp;gt;1     rpcrdma_xprt_disconnect() tail  ep_put        -&amp;gt;0  (ep_destroy) The connect-time get in rpcrdma_xprt_connect(), taken just before rpcrdma_post_recvs() &amp;#34;while there are outstanding Receives,&amp;#34; is balanced by rpcrdma_xprt_drain. ADDR_CHANGE before ESTABLISHED has no get to consume, so its put drops the count to 1 and the drain put then frees the ep while rpcrdma_xprt_disconnect() still holds a pointer to it. Fix by dispatching on the prior re_connect_status via xchg(): for prev == 0 (pre-ESTABLISHED) wake the connect waiter and return with no put; for prev == 1 call rpcrdma_force_disconnect() and return. The case-1 arm relies on the subsequent RDMA_CM_EVENT_DISCONNECTED event -- reliably delivered when rdma_disconnect() is…&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 193 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: xprtrdma: Fix ep kref imbalance on ADDR_CHANGE rpcrdma_cm_event_handler() falls through to the disconnected: label on RDMA_CM_EVENT_ADDR_CHANGE and calls rpcrdma_ep_put() with no matching get when the event arrives before RDMA_CM_EVENT_ESTABLISHED. The kref then underflows during connect teardown and rpcrdma_xprt_disconnect() operates on a freed ep. Reference counts across a normal connection lifecycle:     rpcrdma_ep_create()             kref_init     -&amp;gt;1     rpcrdma_xprt_connect()          ep_get        -&amp;gt;2  (before post_recvs)     RDMA_CM_EVENT_ESTABLISHED       ep_get        -&amp;gt;3     RDMA_CM_EVENT_DISCONNECTED      ep_put        -&amp;gt;2     rpcrdma_xprt_drain()            ep_put        -&amp;gt;1     rpcrdma_xprt_disconnect() tail  ep_put        -&amp;gt;0  (ep_destroy) The connect-time get in rpcrdma_xprt_connect(), taken just before rpcrdma_post_recvs() &amp;#34;while there are outstanding Receives,&amp;#34; is balanced by rpcrdma_xprt_drain. ADDR_CHANGE before ESTABLISHED has no get to consume, so its put drops the count to 1 and the drain put then frees the ep while rpcrdma_xprt_disconnect() still holds a pointer to it. Fix by dispatching on the prior re_connect_status via xchg(): for prev == 0 (pre-ESTABLISHED) wake the connect waiter and return with no put; for prev == 1 call rpcrdma_force_disconnect() and return. The case-1 arm relies on the subsequent RDMA_CM_EVENT_DISCONNECTED event -- reliably delivered when rdma_disconnect() is…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-72469</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>
