<?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>Thu, 01 Oct 2026 10:21:44 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-23118 — rxrpc: Fix data-race warning and potential load/store tearing</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-23118</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 data-race warning and potential load/store tearing&lt;/p&gt;
&lt;p&gt;Fix the following:&lt;/p&gt;
&lt;p&gt;BUG: KCSAN: data-race in rxrpc_peer_keepalive_worker / rxrpc_send_data_packet&lt;/p&gt;
&lt;p&gt;which is reporting an issue with the reads and writes to -&amp;gt;last_tx_at in:&lt;/p&gt;
&lt;p&gt;conn-&amp;gt;peer-&amp;gt;last_tx_at = ktime_get_seconds();&lt;/p&gt;
&lt;p&gt;and:&lt;/p&gt;
&lt;p&gt;keepalive_at = peer-&amp;gt;last_tx_at + RXRPC_KEEPALIVE_TIME;&lt;/p&gt;
&lt;p&gt;The lockless accesses to these to values aren&amp;#39;t actually a problem as the
read only needs an approximate time of last transmission for the purposes
of deciding whether or not the transmission of a keepalive packet is
warranted yet.&lt;/p&gt;
&lt;p&gt;Also, as -&amp;gt;last_tx_at is a 64-bit value, tearing can occur on a 32-bit
arch.&lt;/p&gt;
&lt;p&gt;Fix both of these by switching to an unsigned int for -&amp;gt;last_tx_at and only
storing the LSW of the time64_t.  It can then be reconstructed at need
provided no more than 68 years has elapsed since the last transmission.&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 data-race warning and potential load/store tearing&lt;/p&gt;
&lt;p&gt;Fix the following:&lt;/p&gt;
&lt;p&gt;BUG: KCSAN: data-race in rxrpc_peer_keepalive_worker / rxrpc_send_data_packet&lt;/p&gt;
&lt;p&gt;which is reporting an issue with the reads and writes to -&amp;gt;last_tx_at in:&lt;/p&gt;
&lt;p&gt;conn-&amp;gt;peer-&amp;gt;last_tx_at = ktime_get_seconds();&lt;/p&gt;
&lt;p&gt;and:&lt;/p&gt;
&lt;p&gt;keepalive_at = peer-&amp;gt;last_tx_at + RXRPC_KEEPALIVE_TIME;&lt;/p&gt;
&lt;p&gt;The lockless accesses to these to values aren&amp;#39;t actually a problem as the
read only needs an approximate time of last transmission for the purposes
of deciding whether or not the transmission of a keepalive packet is
warranted yet.&lt;/p&gt;
&lt;p&gt;Also, as -&amp;gt;last_tx_at is a 64-bit value, tearing can occur on a 32-bit
arch.&lt;/p&gt;
&lt;p&gt;Fix both of these by switching to an unsigned int for -&amp;gt;last_tx_at and only
storing the LSW of the time64_t.  It can then be reconstructed at need
provided no more than 68 years has elapsed since the last transmission.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-23118</guid>
    </item>
  </channel>
</rss>
