public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Sean Young <sean@mess.org>
To: Rohaniyaa <rohanmithari09@gmail.com>
Cc: linux-media@vger.kernel.org,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-kernel@vger.kernel.org,
	syzbot+5d7eece664082e0c5c1a@syzkaller.appspotmail.com
Subject: Re: [PATCH] media: rc: igorplugusb: fix memory corruption race condition in probe
Date: Mon, 4 May 2026 17:43:48 +0100	[thread overview]
Message-ID: <afjMxJQ8Ftzb8kSq@extorris.mess.org> (raw)
In-Reply-To: <20260404183507.773866-1-rohanmithari09@gmail.com>

Hi,

On Sun, Apr 05, 2026 at 12:05:07AM +0530, Rohaniyaa wrote:
> From: Rohan Mithari <rohanmithari09@gmail.com>
> 
> Syzbot reported a race condition causing a WARNING in usb_submit_urb.
> 
> In igorplugusb_probe(), the driver registers the RC device via
> rc_register_device() before initializing the internal interface data
> via usb_set_intfdata().
> 
> If the device is abruptly disconnected or accessed by userspace
> immediately after registration, the disconnect function or active URB
> submission can trigger a NULL pointer dereference or Use-After-Free.
> Without KASAN enabled, this race condition silently corrupts the slab
> allocator, leading to a delayed fatal panic in kmem_cache_alloc().
> 
> This patch fixes the race by ensuring the private data (ir) is safely
> attached to the USB interface and the hardware is fully initialized
> before exposing the device to the subsystem via rc_register_device().
> 
> Reported-by: syzbot+5d7eece664082e0c5c1a@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=5d7eece664082e0c5c1a
> 
> Signed-off-by: Rohan Mithari <rohanmithari09@gmail.com>
> ---
>  drivers/media/rc/igorplugusb.c | 14 +++++---------
>  1 file changed, 5 insertions(+), 9 deletions(-)
> 
> diff --git a/drivers/media/rc/igorplugusb.c b/drivers/media/rc/igorplugusb.c
> index 3e10f6fe89f8..a694ed1e5c1f 100644
> --- a/drivers/media/rc/igorplugusb.c
> +++ b/drivers/media/rc/igorplugusb.c
> @@ -214,17 +214,14 @@ static int igorplugusb_probe(struct usb_interface *intf,
>  	rc->rx_resolution = 85;
>  
>  	ir->rc = rc;
> +	usb_set_intfdata(intf, ir);
> +	igorplugusb_cmd(ir, SET_INFRABUFFER_EMPTY);
>  	ret = rc_register_device(rc);
>  	if (ret) {
>  		dev_err(&intf->dev, "failed to register rc device: %d", ret);
>  		goto fail;
> -	}
> -
> -	usb_set_intfdata(intf, ir);
> -
> -	igorplugusb_cmd(ir, SET_INFRABUFFER_EMPTY);
> -

I don't understand how that fixes anything.

> -	return 0;
> +}
> +return 0;

That's messy.

>  fail:
>  	usb_poison_urb(ir->urb);
>  	timer_delete(&ir->timer);
> @@ -233,8 +230,7 @@ static int igorplugusb_probe(struct usb_interface *intf,
>  	rc_free_device(ir->rc);
>  	kfree(ir->buf_in);
>  	kfree(ir->request);
> -
> -	return ret;
> +return ret;

Again, do not do that - that's messy.

Thanks,

Sean

>  }
>  
>  static void igorplugusb_disconnect(struct usb_interface *intf)
> -- 
> 2.34.1
> 

      reply	other threads:[~2026-05-04 16:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-04 18:35 [PATCH] media: rc: igorplugusb: fix memory corruption race condition in probe Rohaniyaa
2026-05-04 16:43 ` Sean Young [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=afjMxJQ8Ftzb8kSq@extorris.mess.org \
    --to=sean@mess.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=rohanmithari09@gmail.com \
    --cc=syzbot+5d7eece664082e0c5c1a@syzkaller.appspotmail.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