<?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-09-29T22:36:50.681963+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-2023-53586</id>
    <title>CVE-2023-53586 — scsi: target: Fix multiple LUN_RESET handling</title>
    <updated>2026-09-29T22:36:50.699794+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: target: Fix multiple LUN_RESET handling</p>
<p>This fixes a bug where an initiator thinks a LUN_RESET has cleaned up
running commands when it hasn't. The bug was added in commit 51ec502a3266
("target: Delete tmr from list before processing").</p>
<p>The problem occurs when:</p>
<p>1. We have N I/O cmds running in the target layer spread over 2 sessions.</p>
<p>2. The initiator sends a LUN_RESET for each session.</p>
<p>3. session1's LUN_RESET loops over all the running commands from both
    sessions and moves them to its local drain_task_list.</p>
<p>4. session2's LUN_RESET does not see the LUN_RESET from session1 because
    the commit above has it remove itself. session2 also does not see any
    commands since the other reset moved them off the state lists.</p>
<p>5. sessions2's LUN_RESET will then complete with a successful response.</p>
<p>6. sessions2's inititor believes the running commands on its session are
    now cleaned up due to the successful response and cleans up the running
    commands from its side. It then restarts them.</p>
<p>7. The commands do eventually complete on the backend and the target
    starts to return aborted task statuses for them. The initiator will
    either throw a invalid ITT error or might accidentally lookup a new
    task if the ITT has been reallocated already.</p>
<p>Fix the bug by reverting the patch, and serialize the execution of
LUN_RESETs and Preempt and Aborts.</p>
<p>Also prevent us from waiting on LUN_RES…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2023-53586"/>
  </entry>
</feed>
