<?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 16:27:12 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-89654</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-89654</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-89654</guid>
    </item>
    <item>
      <title>EUVD-2026-367326</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-367326</link>
      <description>EUVD-2026-367326</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-367326</guid>
    </item>
    <item>
      <title>fkie_cve-2026-89654</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-89654</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ceph: fix UAF in check_new_map() on session freed during unlock&lt;/p&gt;
&lt;p&gt;check_new_map() iterates mdsc-&amp;gt;sessions[] and for each active session
drops mdsc-&amp;gt;mutex to perform per-session operations.  The forced-close
path (rank removed from map) correctly takes a reference on s via
ceph_get_mds_session() before releasing mdsc-&amp;gt;mutex, but three other
paths do not:&lt;/p&gt;
&lt;p&gt;Path A (address changed):  mutex_unlock → mutex_lock(&amp;amp;s-&amp;gt;s_mutex)
  Path B (reconnect):        mutex_unlock → send_mds_reconnect(mdsc, s)
  Path C (active transition): mutex_unlock → mutex_lock(&amp;amp;s-&amp;gt;s_mutex)&lt;/p&gt;
&lt;p&gt;Without the extra reference, another thread can acquire mdsc-&amp;gt;mutex
during the unlock window, call __unregister_session() which drops the
last reference on s, and free it.  The original thread then accesses
freed memory via s-&amp;gt;s_mutex.&lt;/p&gt;
&lt;p&gt;Fix by adding ceph_get_mds_session(s) before each mutex_unlock and
ceph_put_mds_session(s) after the corresponding mutex_lock, matching
the pattern already used in the forced-close path.&lt;/p&gt;
&lt;p&gt;Race timeline (Path A):&lt;/p&gt;
&lt;p&gt;Thread A (check_new_map)             Thread B (another map update
    holds mdsc-&amp;gt;mutex                      or session teardown)
  --------------------------           --------------------------
  s = mdsc-&amp;gt;sessions[i]
  (refcount == 1, held only by
   sessions[] array)&lt;/p&gt;
&lt;p&gt;mutex_unlock(&amp;amp;mdsc-&amp;gt;mutex)
                               ---&amp;gt;    acquires mdsc-&amp;gt;mutex
                                       __unregiste…&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;ceph: fix UAF in check_new_map() on session freed during unlock&lt;/p&gt;
&lt;p&gt;check_new_map() iterates mdsc-&amp;gt;sessions[] and for each active session
drops mdsc-&amp;gt;mutex to perform per-session operations.  The forced-close
path (rank removed from map) correctly takes a reference on s via
ceph_get_mds_session() before releasing mdsc-&amp;gt;mutex, but three other
paths do not:&lt;/p&gt;
&lt;p&gt;Path A (address changed):  mutex_unlock → mutex_lock(&amp;amp;s-&amp;gt;s_mutex)
  Path B (reconnect):        mutex_unlock → send_mds_reconnect(mdsc, s)
  Path C (active transition): mutex_unlock → mutex_lock(&amp;amp;s-&amp;gt;s_mutex)&lt;/p&gt;
&lt;p&gt;Without the extra reference, another thread can acquire mdsc-&amp;gt;mutex
during the unlock window, call __unregister_session() which drops the
last reference on s, and free it.  The original thread then accesses
freed memory via s-&amp;gt;s_mutex.&lt;/p&gt;
&lt;p&gt;Fix by adding ceph_get_mds_session(s) before each mutex_unlock and
ceph_put_mds_session(s) after the corresponding mutex_lock, matching
the pattern already used in the forced-close path.&lt;/p&gt;
&lt;p&gt;Race timeline (Path A):&lt;/p&gt;
&lt;p&gt;Thread A (check_new_map)             Thread B (another map update
    holds mdsc-&amp;gt;mutex                      or session teardown)
  --------------------------           --------------------------
  s = mdsc-&amp;gt;sessions[i]
  (refcount == 1, held only by
   sessions[] array)&lt;/p&gt;
&lt;p&gt;mutex_unlock(&amp;amp;mdsc-&amp;gt;mutex)
                               ---&amp;gt;    acquires mdsc-&amp;gt;mutex
                                       __unregiste…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-89654</guid>
    </item>
    <item>
      <title>GHSA-hwg3-wmfr-8q53</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-hwg3-wmfr-8q53</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ceph: fix UAF in check_new_map() on session freed during unlock&lt;/p&gt;
&lt;p&gt;check_new_map() iterates mdsc-&amp;gt;sessions[] and for each active session
drops mdsc-&amp;gt;mutex to perform per-session operations.  The forced-close
path (rank removed from map) correctly takes a reference on s via
ceph_get_mds_session() before releasing mdsc-&amp;gt;mutex, but three other
paths do not:&lt;/p&gt;
&lt;p&gt;Path A (address changed):  mutex_unlock → mutex_lock(&amp;amp;s-&amp;gt;s_mutex)
  Path B (reconnect):        mutex_unlock → send_mds_reconnect(mdsc, s)
  Path C (active transition): mutex_unlock → mutex_lock(&amp;amp;s-&amp;gt;s_mutex)&lt;/p&gt;
&lt;p&gt;Without the extra reference, another thread can acquire mdsc-&amp;gt;mutex
during the unlock window, call __unregister_session() which drops the
last reference on s, and free it.  The original thread then accesses
freed memory via s-&amp;gt;s_mutex.&lt;/p&gt;
&lt;p&gt;Fix by adding ceph_get_mds_session(s) before each mutex_unlock and
ceph_put_mds_session(s) after the corresponding mutex_lock, matching
the pattern already used in the forced-close path.&lt;/p&gt;
&lt;p&gt;Race timeline (Path A):&lt;/p&gt;
&lt;p&gt;Thread A (check_new_map)             Thread B (another map update
    holds mdsc-&amp;gt;mutex                      or session teardown)
  --------------------------           --------------------------
  s = mdsc-&amp;gt;sessions[i]
  (refcount == 1, held only by
   sessions[] array)&lt;/p&gt;
&lt;p&gt;mutex_unlock(&amp;amp;mdsc-&amp;gt;mutex)
                               ---&amp;gt;    acquires mdsc-&amp;gt;mutex
                                       __unregiste…&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;ceph: fix UAF in check_new_map() on session freed during unlock&lt;/p&gt;
&lt;p&gt;check_new_map() iterates mdsc-&amp;gt;sessions[] and for each active session
drops mdsc-&amp;gt;mutex to perform per-session operations.  The forced-close
path (rank removed from map) correctly takes a reference on s via
ceph_get_mds_session() before releasing mdsc-&amp;gt;mutex, but three other
paths do not:&lt;/p&gt;
&lt;p&gt;Path A (address changed):  mutex_unlock → mutex_lock(&amp;amp;s-&amp;gt;s_mutex)
  Path B (reconnect):        mutex_unlock → send_mds_reconnect(mdsc, s)
  Path C (active transition): mutex_unlock → mutex_lock(&amp;amp;s-&amp;gt;s_mutex)&lt;/p&gt;
&lt;p&gt;Without the extra reference, another thread can acquire mdsc-&amp;gt;mutex
during the unlock window, call __unregister_session() which drops the
last reference on s, and free it.  The original thread then accesses
freed memory via s-&amp;gt;s_mutex.&lt;/p&gt;
&lt;p&gt;Fix by adding ceph_get_mds_session(s) before each mutex_unlock and
ceph_put_mds_session(s) after the corresponding mutex_lock, matching
the pattern already used in the forced-close path.&lt;/p&gt;
&lt;p&gt;Race timeline (Path A):&lt;/p&gt;
&lt;p&gt;Thread A (check_new_map)             Thread B (another map update
    holds mdsc-&amp;gt;mutex                      or session teardown)
  --------------------------           --------------------------
  s = mdsc-&amp;gt;sessions[i]
  (refcount == 1, held only by
   sessions[] array)&lt;/p&gt;
&lt;p&gt;mutex_unlock(&amp;amp;mdsc-&amp;gt;mutex)
                               ---&amp;gt;    acquires mdsc-&amp;gt;mutex
                                       __unregiste…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-hwg3-wmfr-8q53</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11880-1 — kernel-devel-7.2.7-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:11880-1</link>
      <description>&lt;p&gt;kernel-devel-7.2.7-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.2.7-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:11880-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-89654</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-89654</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ceph: fix UAF in check_new_map() on session freed during unlock check_new_map() iterates mdsc-&amp;gt;sessions[] and for each active session drops mdsc-&amp;gt;mutex to perform per-session operations.  The forced-close path (rank removed from map) correctly takes a reference on s via ceph_get_mds_session() before releasing mdsc-&amp;gt;mutex, but three other paths do not:   Path A (address changed):  mutex_unlock → mutex_lock(&amp;amp;s-&amp;gt;s_mutex)   Path B (reconnect):        mutex_unlock → send_mds_reconnect(mdsc, s)   Path C (active transition): mutex_unlock → mutex_lock(&amp;amp;s-&amp;gt;s_mutex) Without the extra reference, another thread can acquire mdsc-&amp;gt;mutex during the unlock window, call __unregister_session() which drops the last reference on s, and free it.  The original thread then accesses freed memory via s-&amp;gt;s_mutex. Fix by adding ceph_get_mds_session(s) before each mutex_unlock and ceph_put_mds_session(s) after the corresponding mutex_lock, matching the pattern already used in the forced-close path. Race timeline (Path A):   Thread A (check_new_map)             Thread B (another map update     holds mdsc-&amp;gt;mutex                      or session teardown)   --------------------------           --------------------------   s = mdsc-&amp;gt;sessions[i]   (refcount == 1, held only by    sessions[] array)   mutex_unlock(&amp;amp;mdsc-&amp;gt;mutex)                                ---&amp;gt;    acquires mdsc-&amp;gt;mutex                                        __unregister_sessio…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ceph: fix UAF in check_new_map() on session freed during unlock check_new_map() iterates mdsc-&amp;gt;sessions[] and for each active session drops mdsc-&amp;gt;mutex to perform per-session operations.  The forced-close path (rank removed from map) correctly takes a reference on s via ceph_get_mds_session() before releasing mdsc-&amp;gt;mutex, but three other paths do not:   Path A (address changed):  mutex_unlock → mutex_lock(&amp;amp;s-&amp;gt;s_mutex)   Path B (reconnect):        mutex_unlock → send_mds_reconnect(mdsc, s)   Path C (active transition): mutex_unlock → mutex_lock(&amp;amp;s-&amp;gt;s_mutex) Without the extra reference, another thread can acquire mdsc-&amp;gt;mutex during the unlock window, call __unregister_session() which drops the last reference on s, and free it.  The original thread then accesses freed memory via s-&amp;gt;s_mutex. Fix by adding ceph_get_mds_session(s) before each mutex_unlock and ceph_put_mds_session(s) after the corresponding mutex_lock, matching the pattern already used in the forced-close path. Race timeline (Path A):   Thread A (check_new_map)             Thread B (another map update     holds mdsc-&amp;gt;mutex                      or session teardown)   --------------------------           --------------------------   s = mdsc-&amp;gt;sessions[i]   (refcount == 1, held only by    sessions[] array)   mutex_unlock(&amp;amp;mdsc-&amp;gt;mutex)                                ---&amp;gt;    acquires mdsc-&amp;gt;mutex                                        __unregister_sessio…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-89654</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3321 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3321</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsmaßnahmen zu umgehen, Daten oder den Systemzustand zu manipulieren, Denial-of-Service-Zustände herbeizuführen oder andere, nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsmaßnahmen zu umgehen, Daten oder den Systemzustand zu manipulieren, Denial-of-Service-Zustände herbeizuführen oder andere, nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3321</guid>
    </item>
  </channel>
</rss>
