mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sean Young <sean@mess.org>
To: joasantonio108@gmail.com
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org,
	syzbot+aec1962419768c5caf88@syzkaller.appspotmail.com
Subject: Re: [PATCH] media: rc: redrat3: fix use-after-free of input device name/phys strings
Date: Sun, 8 Nov 2026 14:06:06 +0000	[thread overview]
Message-ID: <avCBzjIenoErsXhh@extorris.mess.org> (raw)
In-Reply-To: <20261104-redrat3-input-uaf-v1-1-b882e43d9803@gmail.com>

On Wed, Nov 04, 2026 at 09:03:01PM +0000, Joas Antonio dos Santos via B4 Relay wrote:
> From: Joas Antonio dos Santos <joasantonio108@gmail.com>
> 
> redrat3_init_rc_dev() sets rc->device_name and rc->input_phys to point
> at the name[] and phys[] arrays embedded in struct redrat3_dev.
> rc_prepare_rx_device() then copies these pointers into input_dev->name
> and input_dev->phys without duplicating the strings.
> 
> When redrat3_dev_disconnect() runs, it calls redrat3_delete() which
> kfrees the redrat3_dev struct, freeing the embedded name and phys
> arrays.  If an evdev client still holds the input device open, a
> subsequent EVIOCGNAME or EVIOCGPHYS ioctl calls str_to_user() which
> reads the freed string via strlen(), triggering a KASAN
> slab-use-after-free on the freed kmalloc-2k object.

This is nonsense. rc_unregister_device() calls input_unregister_device()
so EVIOCGNAME will not work any more.

My guess this syzbot issue is resolved by commit
af452b9e01331b5338a1e5141624f17607239207 and this is the error path in probe,
not disconnect..


Sean

> 
> Fix by allocating the name and phys strings with devm_kasprintf() and
> devm_kzalloc() respectively, tied to the USB interface device lifetime.
> This ensures the strings outlive the input device, since the USB
> interface device (and its devres) is not released until all references
> to it are dropped.
> 
> Found by LLM-assisted code review of syzbot-reported crash patterns.
> 
> Reported-by: syzbot+aec1962419768c5caf88@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=aec1962419768c5caf88
> Fixes: 2154be651bfd ("[media] redrat3: new driver")
> Cc: stable@vger.kernel.org
> Signed-off-by: Joas Antonio dos Santos <joasantonio108@gmail.com>
> ---
> redrat3_init_rc_dev() stores pointers to the name[] and phys[] arrays
> embedded in struct redrat3_dev into rc->device_name and rc->input_phys.
> These are copied into input_dev->name/phys without duplication.
> 
> When the device disconnects, kfree(rr3) frees the strings while evdev
> may still hold the input device open.  A subsequent EVIOCGNAME ioctl
> dereferences the freed string via str_to_user() -> strlen(), triggering
> a KASAN slab-use-after-free.
> 
> syzbot link: https://syzkaller.appspot.com/bug?extid=aec1962419768c5caf88
> ---
>  drivers/media/rc/redrat3.c | 17 +++++++++++------
>  1 file changed, 11 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/media/rc/redrat3.c b/drivers/media/rc/redrat3.c
> index 3e82b5e66..d9e37ede2 100644
> --- a/drivers/media/rc/redrat3.c
> +++ b/drivers/media/rc/redrat3.c
> @@ -229,8 +229,8 @@ struct redrat3_dev {
>  
>  	u32 carrier;
>  
> -	char name[64];
> -	char phys[64];
> +	char *name;
> +	char *phys;
>  };
>  
>  static void redrat3_dump_fw_error(struct redrat3_dev *rr3, int code)
> @@ -943,11 +943,16 @@ static struct rc_dev *redrat3_init_rc_dev(struct redrat3_dev *rr3)
>  	if (!rc)
>  		return NULL;
>  
> -	snprintf(rr3->name, sizeof(rr3->name),
> -		 "RedRat3%s Infrared Remote Transceiver",
> -		 prod == USB_RR3IIUSB_PRODUCT_ID ? "-II" : "");
> +	rr3->name = devm_kasprintf(rr3->dev, GFP_KERNEL,
> +				   "RedRat3%s Infrared Remote Transceiver",
> +				   prod == USB_RR3IIUSB_PRODUCT_ID ? "-II" : "");
> +	if (!rr3->name)
> +		goto out;
>  
> -	usb_make_path(rr3->udev, rr3->phys, sizeof(rr3->phys));
> +	rr3->phys = devm_kzalloc(rr3->dev, 64, GFP_KERNEL);
> +	if (!rr3->phys)
> +		goto out;
> +	usb_make_path(rr3->udev, rr3->phys, 64);
>  
>  	rc->device_name = rr3->name;
>  	rc->input_phys = rr3->phys;
> 
> ---
> base-commit: 05441d697f7f9a927264f4058cbbc6a03dfcac9d
> change-id: 20261104-redrat3-input-uaf-b6d3789e63c9
> 
> Best regards,
> -- 
> Joas Antonio dos Santos <joasantonio108@gmail.com>
> 
> 

  reply	other threads:[~2026-11-08 14:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-04 21:03 Joas Antonio dos Santos via B4 Relay
2026-11-08 14:06 ` Sean Young [this message]
2026-11-08 16:44   ` Joas Antonio

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=avCBzjIenoErsXhh@extorris.mess.org \
    --to=sean@mess.org \
    --cc=joasantonio108@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=syzbot+aec1962419768c5caf88@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

all inboxes | Powered by JetHome®