The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Phillip Potter <phil@philpotter.co.uk>
To: raoxu <raoxu@uniontech.com>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	phil@philpotter.co.uk
Subject: Re: [PATCH] cdrom: fix stack out-of-bounds read in CDROMVOLCTRL
Date: Fri, 17 Jul 2026 08:11:48 +0100	[thread overview]
Message-ID: <alnVtDdoB7Zs4wfe@equinox> (raw)
In-Reply-To: <461EA3D17ECF5C5C+20260713082013.3423808-1-raoxu@uniontech.com>

On Mon, Jul 13, 2026 at 04:20:13PM +0800, raoxu wrote:
> From: Xu Rao <raoxu@uniontech.com>
> 
> mmc_ioctl_cdrom_volume() first reads the audio control mode page into a
> 32-byte stack buffer with cgc->buflen set to 24.  If the device reports a
> block descriptor, the function increases cgc->buflen to include that
> descriptor and reads the page again.
> 
> For CDROMVOLCTRL, the function then builds a MODE SELECT parameter list
> by moving cgc->buffer forward by offset - 8 bytes.  This drops the block
> descriptor from the outgoing payload and leaves a new 8-byte mode
> parameter header in front of the audio control page.  However, cgc->buflen
> is left unchanged.
> 
> With a standard 8-byte block descriptor, cgc->buffer points at buffer + 8
> but cgc->buflen remains 32.  cdrom_mode_select() therefore asks the low
> level packet path to write 32 bytes from that adjusted pointer, reading 8
> bytes past the end of the 32-byte stack buffer.
> 
> This is not hit by CDROMVOLREAD, and CDROMVOLCTRL only triggers it on
> drives that return a non-zero block descriptor length, which helps explain
> why it has gone unnoticed.  The overread is also sent to the device as
> extra MODE SELECT payload, so it may not produce an obvious local failure.
> 
> Reduce cgc->buflen by the same amount as the buffer pointer adjustment so
> the MODE SELECT transfer covers only the intended parameter list.
> 
> Fixes: 3147c531b6b5 ("cdrom: split mmc_ioctl to lower stack usage")
> Cc: stable@vger.kernel.org
> Signed-off-by: Xu Rao <raoxu@uniontech.com>
> ---
>  drivers/cdrom/cdrom.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/cdrom/cdrom.c b/drivers/cdrom/cdrom.c
> index 62934cf4b10d..4f1fd389260f 100644
> --- a/drivers/cdrom/cdrom.c
> +++ b/drivers/cdrom/cdrom.c
> @@ -3187,6 +3187,7 @@ static noinline int mmc_ioctl_cdrom_volume(struct cdrom_device_info *cdi,
>  
>  	/* set volume */
>  	cgc->buffer = buffer + offset - 8;
> +	cgc->buflen -= offset - 8;
>  	memset(cgc->buffer, 0, 8);
>  	return cdrom_mode_select(cdi, cgc);
>  }
> -- 
> 2.50.1
> 

Hi Xu Rao,

Thanks for your patch. I will endeavour to look at it and verify it this
weekend and come back to you.

Regards,
Phil

  reply	other threads:[~2026-07-17  7:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-13  8:20 [PATCH] cdrom: fix stack out-of-bounds read in CDROMVOLCTRL raoxu
2026-07-17  7:11 ` Phillip Potter [this message]
2026-07-19 18:40 ` Phillip Potter
2026-07-20  1:31   ` raoxu

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=alnVtDdoB7Zs4wfe@equinox \
    --to=phil@philpotter.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=raoxu@uniontech.com \
    --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