<?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>Tue, 29 Sep 2026 07:21:25 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-74425 — afs: handle CB.InitCallBackState3 requests without a server record</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-74425</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;afs: handle CB.InitCallBackState3 requests without a server record&lt;/p&gt;
&lt;p&gt;The cache manager callback path now attaches the server record to an
incoming call through the rxrpc peer&amp;#39;s app data.  That association is
not guaranteed to exist for every callback request, and most callback
handlers already tolerate that case.&lt;/p&gt;
&lt;p&gt;Make CB.InitCallBackState3 follow the same pattern by checking whether a
server record was attached before using it.  If the peer is not mapped
to a server record, trace the request and ignore it, matching the
existing behaviour for other unmatched callback requests.&lt;/p&gt;
&lt;p&gt;This keeps the callback handler consistent with the rest of the cache
manager service and avoids depending on peer state that may not be
available for a given request.&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;afs: handle CB.InitCallBackState3 requests without a server record&lt;/p&gt;
&lt;p&gt;The cache manager callback path now attaches the server record to an
incoming call through the rxrpc peer&amp;#39;s app data.  That association is
not guaranteed to exist for every callback request, and most callback
handlers already tolerate that case.&lt;/p&gt;
&lt;p&gt;Make CB.InitCallBackState3 follow the same pattern by checking whether a
server record was attached before using it.  If the peer is not mapped
to a server record, trace the request and ignore it, matching the
existing behaviour for other unmatched callback requests.&lt;/p&gt;
&lt;p&gt;This keeps the callback handler consistent with the rest of the cache
manager service and avoids depending on peer state that may not be
available for a given request.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-74425</guid>
    </item>
  </channel>
</rss>
