From: Damien Le Moal <dlemoal@kernel.org>
To: Salomon Dushimirimana <salomondush@google.com>
Cc: James.Bottomley@HansenPartnership.com,
damien.lemoal@opensource.wdc.com, jinpu.wang@cloud.ionos.com,
john.g.garry@oracle.com, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org, martin.petersen@oracle.com
Subject: Re: [PATCH v3] scsi: pm8001: Fix use-after-free in pm8001_queue_command()
Date: Tue, 17 Feb 2026 12:35:42 +0900 [thread overview]
Message-ID: <093cccbf-1477-478c-be6c-ce1a69cf4de7@kernel.org> (raw)
In-Reply-To: <20260213192806.439432-1-salomondush@google.com>
On 2/14/26 04:28, Salomon Dushimirimana wrote:
> Commit e29c47fe8946 ("scsi: pm8001: Simplify pm8001_task_exec()")
> refactors pm8001_queue_command(), however it introduces a potential
> cause of a double free scenario when it changes the function to return
> -ENODEV in case of phy down/device gone state.
>
> In this path, pm8001_queue_command updates task status and calls
> task_done to indicate to upper layer that the task has been handled.
> However, this also frees the underlying sas task. A -ENODEV is then
> returned to the caller. When libsas sas_ata_qc_issue receives this error
> value, it assumes the task wasn't handled/queued by LLDD and proceeds to
> clean up and free the task again, resulting in a double free.
>
> Since pm8001_queue_command handles the sas task in this case, it should
> return 0 to the caller indicating that the task has been handled.
>
> Fixes: e29c47fe8946 ("scsi: pm8001: Simplify pm8001_task_exec()")
> Signed-off-by: Salomon Dushimirimana <salomondush@google.com>
Looks OK.
Reviewed-by: Damien Le Moal <dlemoal@kernel.org>
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2026-02-17 3:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 1:07 [PATCH] " Salomon Dushimirimana
2026-02-11 1:28 ` Damien Le Moal
2026-02-13 19:22 ` [PATCH v2] " Salomon Dushimirimana
2026-02-13 19:28 ` [PATCH v3] " Salomon Dushimirimana
2026-02-17 3:35 ` Damien Le Moal [this message]
2026-02-18 2:36 ` Martin K. Petersen
2026-02-24 16:47 ` Martin K. Petersen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=093cccbf-1477-478c-be6c-ce1a69cf4de7@kernel.org \
--to=dlemoal@kernel.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=jinpu.wang@cloud.ionos.com \
--cc=john.g.garry@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=salomondush@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome