<?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>Tue, 06 Oct 2026 00:41:49 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-48792 — scsi: pm8001: Fix use-after-free for aborted SSP/STP sas_task</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2022-48792</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;scsi: pm8001: Fix use-after-free for aborted SSP/STP sas_task&lt;/p&gt;
&lt;p&gt;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().&lt;/p&gt;
&lt;p&gt;In this case, the following are the two steps in handling those I/O
completions:&lt;/p&gt;
&lt;p&gt;- Call complete() to inform the upper layer handler of completion of
   the I/O.&lt;/p&gt;
&lt;p&gt;- Release driver resources associated with the sas_task in
   pm8001_ccb_task_free() call.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Fix by swapping the complete() and pm8001_ccb_task_free() calls ordering.&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;scsi: pm8001: Fix use-after-free for aborted SSP/STP sas_task&lt;/p&gt;
&lt;p&gt;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().&lt;/p&gt;
&lt;p&gt;In this case, the following are the two steps in handling those I/O
completions:&lt;/p&gt;
&lt;p&gt;- Call complete() to inform the upper layer handler of completion of
   the I/O.&lt;/p&gt;
&lt;p&gt;- Release driver resources associated with the sas_task in
   pm8001_ccb_task_free() call.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Fix by swapping the complete() and pm8001_ccb_task_free() calls ordering.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2022-48792</guid>
    </item>
  </channel>
</rss>
