public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: "Gustavo A. R. Silva" <gustavoars@kernel.org>
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	Torsten Schenk <torsten.schenk@zoho.com>,
	alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
	linux-hardening@vger.kernel.org
Subject: Re: [PATCH][next] ALSA: 6fire: Fix undefined behavior bug in struct midi_runtime
Date: Fri, 06 Oct 2023 11:01:37 +0200	[thread overview]
Message-ID: <87o7hcw2dq.wl-tiwai@suse.de> (raw)
In-Reply-To: <ZRb2CKHuaCu0u38i@work>

On Fri, 29 Sep 2023 18:06:32 +0200,
Gustavo A. R. Silva wrote:
> 
> `struct urb` is a flexible structure, which means that it contains a
> flexible-array member at the bottom. This could potentially lead to an
> overwrite of the objects following `out_urb` in `struct midi_runtime`,
> among them a function pointer.
> 
> Fix this by placing the declaration of object `out_urb` at the end of
> `struct midi_runtime`.
> 
> Fixes: c6d43ba816d1 ("ALSA: usb/6fire - Driver for TerraTec DMX 6Fire USB")
> Cc: stable@vger.kernel.org
> Signed-off-by: Gustavo A. R. Silva <gustavoars@kernel.org>

The same question as your another 6fire patch is applied here: does it
"fix" anything real?


thanks,

Takashi

> ---
>  sound/usb/6fire/midi.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/sound/usb/6fire/midi.h b/sound/usb/6fire/midi.h
> index 47640c845903..df3f41913274 100644
> --- a/sound/usb/6fire/midi.h
> +++ b/sound/usb/6fire/midi.h
> @@ -22,12 +22,12 @@ struct midi_runtime {
>  	spinlock_t in_lock;
>  	spinlock_t out_lock;
>  	struct snd_rawmidi_substream *out;
> -	struct urb out_urb;
>  	u8 out_serial; /* serial number of out packet */
>  	u8 *out_buffer;
>  	int buffer_offset;
>  
>  	void (*in_received)(struct midi_runtime *rt, u8 *data, int length);
> +	struct urb out_urb;
>  };
>  
>  int usb6fire_midi_init(struct sfire_chip *chip);
> -- 
> 2.34.1
> 

      parent reply	other threads:[~2023-10-06  9:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-29 16:06 [PATCH][next] ALSA: 6fire: Fix undefined behavior bug in struct midi_runtime Gustavo A. R. Silva
2023-09-29 17:27 ` Kees Cook
2023-10-01  6:53   ` Gustavo A. R. Silva
2023-10-06  9:01 ` Takashi Iwai [this message]

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=87o7hcw2dq.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=gustavoars@kernel.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.com \
    --cc=torsten.schenk@zoho.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