<?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>Wed, 30 Sep 2026 13:56:57 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-68156 — libceph: refresh auth-&gt;authorizer_buf{,_len} after authorizer update</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-68156</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;libceph: refresh auth-&amp;gt;authorizer_buf{,_len} after authorizer update&lt;/p&gt;
&lt;p&gt;ceph_x_create_authorizer() caches au-&amp;gt;buf-&amp;gt;vec.iov_base and
au-&amp;gt;buf-&amp;gt;vec.iov_len in struct ceph_auth_handshake.  These
cached values are then used by the messenger connect code when
sending the authorizer.&lt;/p&gt;
&lt;p&gt;ceph_x_update_authorizer() can rebuild the authorizer when a newer
service ticket is available.  If the rebuilt authorizer no longer
fits in the existing buffer, ceph_x_build_authorizer() drops its
reference to au-&amp;gt;buf and allocates a new one.  If this is the final
reference, ceph_buffer_put() frees the old ceph_buffer and its
vec.iov_base, but auth-&amp;gt;authorizer_buf still points at that freed
memory.&lt;/p&gt;
&lt;p&gt;A subsequent msgr1 reconnect can therefore queue the stale pointer
and trigger a KASAN slab-use-after-free in _copy_from_iter() while
tcp_sendmsg() copies the authorizer.&lt;/p&gt;
&lt;p&gt;Refresh auth-&amp;gt;authorizer_buf and auth-&amp;gt;authorizer_buf_len after a
successful authorizer rebuild so the messenger sends the current
buffer.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;libceph: refresh auth-&amp;gt;authorizer_buf{,_len} after authorizer update&lt;/p&gt;
&lt;p&gt;ceph_x_create_authorizer() caches au-&amp;gt;buf-&amp;gt;vec.iov_base and
au-&amp;gt;buf-&amp;gt;vec.iov_len in struct ceph_auth_handshake.  These
cached values are then used by the messenger connect code when
sending the authorizer.&lt;/p&gt;
&lt;p&gt;ceph_x_update_authorizer() can rebuild the authorizer when a newer
service ticket is available.  If the rebuilt authorizer no longer
fits in the existing buffer, ceph_x_build_authorizer() drops its
reference to au-&amp;gt;buf and allocates a new one.  If this is the final
reference, ceph_buffer_put() frees the old ceph_buffer and its
vec.iov_base, but auth-&amp;gt;authorizer_buf still points at that freed
memory.&lt;/p&gt;
&lt;p&gt;A subsequent msgr1 reconnect can therefore queue the stale pointer
and trigger a KASAN slab-use-after-free in _copy_from_iter() while
tcp_sendmsg() copies the authorizer.&lt;/p&gt;
&lt;p&gt;Refresh auth-&amp;gt;authorizer_buf and auth-&amp;gt;authorizer_buf_len after a
successful authorizer rebuild so the messenger sends the current
buffer.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-68156</guid>
    </item>
  </channel>
</rss>
