<?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 10:03:06 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-31630 — rxrpc: proc: size address buffers for %pISpc output</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-31630</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: proc: size address buffers for %pISpc output&lt;/p&gt;
&lt;p&gt;The AF_RXRPC procfs helpers format local and remote socket addresses into
fixed 50-byte stack buffers with &amp;#34;%pISpc&amp;#34;.&lt;/p&gt;
&lt;p&gt;That is too small for the longest current-tree IPv6-with-port form the
formatter can produce. In lib/vsprintf.c, the compressed IPv6 path uses a
dotted-quad tail not only for v4mapped addresses, but also for ISATAP
addresses via ipv6_addr_is_isatap().&lt;/p&gt;
&lt;p&gt;As a result, a case such as&lt;/p&gt;
&lt;p&gt;[ffff:ffff:ffff:ffff:0:5efe:255.255.255.255]:65535&lt;/p&gt;
&lt;p&gt;is possible with the current formatter. That is 50 visible characters, so
51 bytes including the trailing NUL, which does not fit in the existing
char[50] buffers used by net/rxrpc/proc.c.&lt;/p&gt;
&lt;p&gt;Size the buffers from the formatter&amp;#39;s maximum textual form and switch the
call sites to scnprintf().&lt;/p&gt;
&lt;p&gt;Changes since v1:
- correct the changelog to cite the actual maximum current-tree case
  explicitly
- frame the proof around the ISATAP formatting path instead of the earlier
  mapped-v4 example&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: proc: size address buffers for %pISpc output&lt;/p&gt;
&lt;p&gt;The AF_RXRPC procfs helpers format local and remote socket addresses into
fixed 50-byte stack buffers with &amp;#34;%pISpc&amp;#34;.&lt;/p&gt;
&lt;p&gt;That is too small for the longest current-tree IPv6-with-port form the
formatter can produce. In lib/vsprintf.c, the compressed IPv6 path uses a
dotted-quad tail not only for v4mapped addresses, but also for ISATAP
addresses via ipv6_addr_is_isatap().&lt;/p&gt;
&lt;p&gt;As a result, a case such as&lt;/p&gt;
&lt;p&gt;[ffff:ffff:ffff:ffff:0:5efe:255.255.255.255]:65535&lt;/p&gt;
&lt;p&gt;is possible with the current formatter. That is 50 visible characters, so
51 bytes including the trailing NUL, which does not fit in the existing
char[50] buffers used by net/rxrpc/proc.c.&lt;/p&gt;
&lt;p&gt;Size the buffers from the formatter&amp;#39;s maximum textual form and switch the
call sites to scnprintf().&lt;/p&gt;
&lt;p&gt;Changes since v1:
- correct the changelog to cite the actual maximum current-tree case
  explicitly
- frame the proof around the ISATAP formatting path instead of the earlier
  mapped-v4 example&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-31630</guid>
    </item>
  </channel>
</rss>
