From: Damien Le Moal <dlemoal@kernel.org>
To: Mikhail Ukhin <mish.uxin2012@yandex.ru>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jens Axboe <axboe@kernel.dk>, Niklas Cassel <cassel@kernel.org>
Cc: stable@vger.kernel.org, linux-ide@vger.kernel.org,
linux-kernel@vger.kernel.org,
Pavel Koshutin <koshutin.pavel@yandex.ru>,
lvc-project@linuxtesting.org
Subject: Re: [PATCH v4 5.10/5.15] ata: libata-scsi: check cdb length for VARIABLE_LENGTH_CMD commands
Date: Thu, 27 Jun 2024 11:02:23 +0900 [thread overview]
Message-ID: <ab75136a-cdf5-4eb1-a09a-bc59beb6b8df@kernel.org> (raw)
In-Reply-To: <20240626211358.148625-1-mish.uxin2012@yandex.ru>
On 6/27/24 06:13, Mikhail Ukhin wrote:
> Fuzzing of 5.10 stable branch reports a slab-out-of-bounds error in
> ata_scsi_pass_thru.
>
> The error is fixed in 5.18 by commit ce70fd9a551a ("scsi: core: Remove the
> cmd field from struct scsi_request") upstream.
> Backporting this commit would require significant changes to the code so
> it is bettter to use a simple fix for that particular error.
This sentence is not needed in the commit message. That is a discussion to have
when applying (or not) the patch.
>
> The problem is that the length of the received SCSI command is not
> validated if scsi_op == VARIABLE_LENGTH_CMD. It can lead to out-of-bounds
> reading if the user sends a request with SCSI command of length less than
> 32.
>
> Found by Linux Verification Center (linuxtesting.org) with Syzkaller.
>
> Signed-off-by: Artem Sadovnikov <ancowi69@gmail.com>
> Signed-off-by: Mikhail Ivanov <iwanov-23@bk.ru>
> Signed-off-by: Mikhail Ukhin <mish.uxin2012@yandex.ru>
Please send patches for libata to the ata maintainers (Niklas and myself).
Use scripts/get_maintainer.pl And you will get our addresses and see that there
is no need to spam Jens with libata patches.
> ---
> v2: The new addresses were added and the text was updated.
> v3: Checking has been moved to the function ata_scsi_var_len_cdb_xlat at
> the request of Damien Le Moal.
> v4: Extra opcode check removed.
> drivers/ata/libata-scsi.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/ata/libata-scsi.c b/drivers/ata/libata-scsi.c
> index dfa090ccd21c..38488bd813d1 100644
> --- a/drivers/ata/libata-scsi.c
> +++ b/drivers/ata/libata-scsi.c
> @@ -3948,7 +3948,11 @@ static unsigned int ata_scsi_var_len_cdb_xlat(struct ata_queued_cmd *qc)
> struct scsi_cmnd *scmd = qc->scsicmd;
> const u8 *cdb = scmd->cmnd;
> const u16 sa = get_unaligned_be16(&cdb[8]);
>
> + if (scmd->cmd_len < 32)
Given that the only service action supported is ATA_32, this check should be
if (scmd->cmd_len != 32
> + return 1;
> +
> /*
> * if service action represents a ata pass-thru(32) command,
> * then pass it to ata_scsi_pass_thru handler.
> --
> 2.25.1
>
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2024-06-27 2:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 21:13 [PATCH v4 5.10/5.15] ata: libata-scsi: check cdb length for VARIABLE_LENGTH_CMD commands Mikhail Ukhin
2024-06-27 2:02 ` Damien Le Moal [this message]
2024-06-27 20:08 ` Sasha Levin
2024-06-28 3:44 ` Damien Le Moal
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=ab75136a-cdf5-4eb1-a09a-bc59beb6b8df@kernel.org \
--to=dlemoal@kernel.org \
--cc=axboe@kernel.dk \
--cc=cassel@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=koshutin.pavel@yandex.ru \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=mish.uxin2012@yandex.ru \
--cc=stable@vger.kernel.org \
/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