mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hans de Goede <hansg@kernel.org>
To: Wei Jie LAW <98lawweijie@gmail.com>,
	laurent.pinchart@ideasonboard.com, mchehab@kernel.org
Cc: guennadi.liakhovetski@linux.intel.com,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org, ribalda@chromium.org
Subject: Re: [PATCH v2] media: uvcvideo: Fix NULL deref on events for uninitialized controls
Date: Tue, 29 Sep 2026 17:13:17 +0200	[thread overview]
Message-ID: <6534f8fc-6222-4524-881b-d0be69d461ce@kernel.org> (raw)
In-Reply-To: <20260907121844.2592492-1-98lawweijie@gmail.com>

Hi,

On 7-Sep-26 14:18, Wei Jie LAW wrote:
> From: Wei Jie Law <98lawweijie@gmail.com>
> 
> A null-ptr-deref exists in v6.12.105 and upstream. KASAN crash log:
> 
>   KASAN: null-ptr-deref in range [0x0000000000000080-0x0000000000000087]
>   Workqueue: events uvc_ctrl_status_event_work
>   RIP: 0010:uvc_ctrl_status_event+0x105/0x280
>    uvc_ctrl_status_event_work+0x82/0x240
>    process_one_work+0x66f/0x10b0
> 
> XU controls are initialized lazily, on the first UVCIOC_CTRL_MAP or
> UVCIOC_CTRL_QUERY.  Until then ctrl->info is all zeroes, so
> info.mappings is not a valid list head, list_empty() returns false, and
> uvc_ctrl_status_event() walks it from a NULL next pointer.
> 
> Fixes: e5225c820c05 ("media: uvcvideo: Send a control event when a Control Change interrupt arrives")
> Cc: stable@vger.kernel.org
> Signed-off-by: Wei Jie Law <98lawweijie@gmail.com>
> Assisted-by: Claude:claude-opus-5
> Reviewed-by: Ricardo Ribalda <ribalda@chromium.org>

Thank you for your patch.

I have merged this into:

https://gitlab.freedesktop.org/linux-media/users/uvc/-/commits/for-next/

Regards,

Hans



> 
> ---
> Changes in v2:
> - dropped comments in code based on review received
> - add Reviewed-by from Ricardo Ribalda
> - drop the former [2/2] patch as it is a duplicate (out-of-bounds read in
>   uvc_ctrl_status_event()): already handled by
>   https://lore.kernel.org/linux-media/20260813-uvc-status-11-v1-1-2cf43e9590b0@chromium.org/
> 
> v1: https://lore.kernel.org/all/20260907062819.2519878-2-98lawweijie@gmail.com/
> ---
>  drivers/media/usb/uvc/uvc_ctrl.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/media/usb/uvc/uvc_ctrl.c b/drivers/media/usb/uvc/uvc_ctrl.c
> index 3ca108b83f1d..ea28c4e819bd 100644
> --- a/drivers/media/usb/uvc/uvc_ctrl.c
> +++ b/drivers/media/usb/uvc/uvc_ctrl.c
> @@ -2209,7 +2209,7 @@ bool uvc_ctrl_status_event_async(struct urb *urb, struct uvc_video_chain *chain,
>  	struct uvc_device *dev = chain->dev;
>  	struct uvc_ctrl_work *w = &dev->async_ctrl;
>  
> -	if (list_empty(&ctrl->info.mappings))
> +	if (!ctrl->initialized || list_empty(&ctrl->info.mappings))
>  		return false;
>  
>  	w->data = data;


      reply	other threads:[~2026-09-29 15:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-07 12:18 Wei Jie LAW
2026-09-29 15:13 ` Hans de Goede [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=6534f8fc-6222-4524-881b-d0be69d461ce@kernel.org \
    --to=hansg@kernel.org \
    --cc=98lawweijie@gmail.com \
    --cc=guennadi.liakhovetski@linux.intel.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=ribalda@chromium.org \
    --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

all inboxes | Powered by JetHome®