<?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>Mon, 28 Sep 2026 08:09:38 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-89481 — nvme-tcp: fix host memory disclosure on R2T for a read command</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-89481</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;nvme-tcp: fix host memory disclosure on R2T for a read command&lt;/p&gt;
&lt;p&gt;nvme_tcp_handle_r2t() does not check the direction of the request the
R2T refers to. A malicious controller can send an R2T for a READ and
the host will answer it: nvme_tcp_setup_h2c_data_pdu() builds the
H2CData header and nvme_tcp_try_send_data() sends the request&amp;#39;s data
buffer. That buffer is the READ destination, so its contents go to the
controller.&lt;/p&gt;
&lt;p&gt;The command then completes normally and nothing is logged.&lt;/p&gt;
&lt;p&gt;Against a test controller that answers every READ with an R2T, a 4096
byte buffered read returned all 4096 bytes, split over two R2Ts. The
pages contained stale kernel data, including an array of struct page
pointers.&lt;/p&gt;
&lt;p&gt;Reject an R2T for a request that is not a write.&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;nvme-tcp: fix host memory disclosure on R2T for a read command&lt;/p&gt;
&lt;p&gt;nvme_tcp_handle_r2t() does not check the direction of the request the
R2T refers to. A malicious controller can send an R2T for a READ and
the host will answer it: nvme_tcp_setup_h2c_data_pdu() builds the
H2CData header and nvme_tcp_try_send_data() sends the request&amp;#39;s data
buffer. That buffer is the READ destination, so its contents go to the
controller.&lt;/p&gt;
&lt;p&gt;The command then completes normally and nothing is logged.&lt;/p&gt;
&lt;p&gt;Against a test controller that answers every READ with an R2T, a 4096
byte buffered read returned all 4096 bytes, split over two R2Ts. The
pages contained stale kernel data, including an array of struct page
pointers.&lt;/p&gt;
&lt;p&gt;Reject an R2T for a request that is not a write.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-89481</guid>
    </item>
  </channel>
</rss>
