<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-01T20:43:42.702695+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-74557</id>
    <title>CVE-2026-74557 — scsi: libiscsi: Fix stale-data leak into the SCSI sense buffer</title>
    <updated>2026-10-01T20:43:42.704088+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>scsi: libiscsi: Fix stale-data leak into the SCSI sense buffer</p>
<p>iscsi_scsi_cmd_rsp() copies the sense data of a SCSI Response from the
target-supplied data segment.  The segment carries a 2-byte sense length
followed by the sense bytes, so it must hold 2 + senselen bytes, but the
bounds check only requires datalen &gt;= senselen:</p>
<p>senselen = get_unaligned_be16(data);
	if (datalen &lt; senselen)
		goto invalid_datalen;
	memcpy(sc-&gt;sense_buffer, data + 2,
	       min_t(uint16_t, senselen, SCSI_SENSE_BUFFERSIZE));</p>
<p>A target that returns a SCSI Response whose datalen equals senselen
(with senselen &lt;= SCSI_SENSE_BUFFERSIZE) makes the memcpy() from data +
2 read up to two bytes past the received data.  Those bytes are stale
conn-&gt;data contents and end up in the command's sense buffer, which is
returned to userspace.</p>
<p>Account for the 2-byte sense length prefix in the check.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-74557"/>
  </entry>
</feed>
