<?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, 10 Oct 2026 15:17:10 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-31642 — rxrpc: Fix call removal to use RCU safe deletion</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-31642</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;rxrpc: Fix call removal to use RCU safe deletion&lt;/p&gt;
&lt;p&gt;Fix rxrpc call removal from the rxnet-&amp;gt;calls list to use list_del_rcu()
rather than list_del_init() to prevent stuffing up reading
/proc/net/rxrpc/calls from potentially getting into an infinite loop.&lt;/p&gt;
&lt;p&gt;This, however, means that list_empty() no longer works on an entry that&amp;#39;s
been deleted from the list, making it harder to detect prior deletion.  Fix
this by:&lt;/p&gt;
&lt;p&gt;Firstly, make rxrpc_destroy_all_calls() only dump the first ten calls that
are unexpectedly still on the list.  Limiting the number of steps means
there&amp;#39;s no need to call cond_resched() or to remove calls from the list
here, thereby eliminating the need for rxrpc_put_call() to check for that.&lt;/p&gt;
&lt;p&gt;rxrpc_put_call() can then be fixed to unconditionally delete the call from
the list as it is the only place that the deletion occurs.&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;rxrpc: Fix call removal to use RCU safe deletion&lt;/p&gt;
&lt;p&gt;Fix rxrpc call removal from the rxnet-&amp;gt;calls list to use list_del_rcu()
rather than list_del_init() to prevent stuffing up reading
/proc/net/rxrpc/calls from potentially getting into an infinite loop.&lt;/p&gt;
&lt;p&gt;This, however, means that list_empty() no longer works on an entry that&amp;#39;s
been deleted from the list, making it harder to detect prior deletion.  Fix
this by:&lt;/p&gt;
&lt;p&gt;Firstly, make rxrpc_destroy_all_calls() only dump the first ten calls that
are unexpectedly still on the list.  Limiting the number of steps means
there&amp;#39;s no need to call cond_resched() or to remove calls from the list
here, thereby eliminating the need for rxrpc_put_call() to check for that.&lt;/p&gt;
&lt;p&gt;rxrpc_put_call() can then be fixed to unconditionally delete the call from
the list as it is the only place that the deletion occurs.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-31642</guid>
    </item>
  </channel>
</rss>
