<?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-05T23:36:16.011768+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-2022-48792</id>
    <title>CVE-2022-48792 — scsi: pm8001: Fix use-after-free for aborted SSP/STP sas_task</title>
    <updated>2026-10-05T23:36:16.015184+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: pm8001: Fix use-after-free for aborted SSP/STP sas_task</p>
<p>Currently a use-after-free may occur if a sas_task is aborted by the upper
layer before we handle the I/O completion in mpi_ssp_completion() or
mpi_sata_completion().</p>
<p>In this case, the following are the two steps in handling those I/O
completions:</p>
<p>- Call complete() to inform the upper layer handler of completion of
   the I/O.</p>
<p>- Release driver resources associated with the sas_task in
   pm8001_ccb_task_free() call.</p>
<p>When complete() is called, the upper layer may free the sas_task. As such,
we should not touch the associated sas_task afterwards, but we do so in the
pm8001_ccb_task_free() call.</p>
<p>Fix by swapping the complete() and pm8001_ccb_task_free() calls ordering.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2022-48792"/>
  </entry>
</feed>
