<?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 08:25:18 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-89543 — sunrpc: fix use-after-free in __rpc_clnt_handle_event and __rpc_clnt_remove_pipedir</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-89543</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;sunrpc: fix use-after-free in __rpc_clnt_handle_event and __rpc_clnt_remove_pipedir&lt;/p&gt;
&lt;p&gt;Normal client creation goes through rpc_setup_pipedir(), which records
clnt-&amp;gt;pipefs_sb, but the mount-event path in __rpc_clnt_handle_event()
calls rpc_setup_pipedir_sb() directly and never refreshes that field.
The umount path also removes the directory without clearing
clnt-&amp;gt;pipefs_sb.&lt;/p&gt;
&lt;p&gt;After a late pipefs mount or any remount, rpc_clnt_remove_pipedir()
compares the current superblock against a stale pipefs_sb pointer and
skips cleanup, leaving pipefs dentries whose inode private data still
points at a freed rpc_clnt, leading to a potential use-after-free during
subsequent rpc_info_open() or rpc_show_info() calls.&lt;/p&gt;
&lt;p&gt;Fix this by properly updating clnt-&amp;gt;pipefs_sb upon mount events and
clearing it during unmount or failure paths.&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;sunrpc: fix use-after-free in __rpc_clnt_handle_event and __rpc_clnt_remove_pipedir&lt;/p&gt;
&lt;p&gt;Normal client creation goes through rpc_setup_pipedir(), which records
clnt-&amp;gt;pipefs_sb, but the mount-event path in __rpc_clnt_handle_event()
calls rpc_setup_pipedir_sb() directly and never refreshes that field.
The umount path also removes the directory without clearing
clnt-&amp;gt;pipefs_sb.&lt;/p&gt;
&lt;p&gt;After a late pipefs mount or any remount, rpc_clnt_remove_pipedir()
compares the current superblock against a stale pipefs_sb pointer and
skips cleanup, leaving pipefs dentries whose inode private data still
points at a freed rpc_clnt, leading to a potential use-after-free during
subsequent rpc_info_open() or rpc_show_info() calls.&lt;/p&gt;
&lt;p&gt;Fix this by properly updating clnt-&amp;gt;pipefs_sb upon mount events and
clearing it during unmount or failure paths.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-89543</guid>
    </item>
  </channel>
</rss>
