From: Wei Jie Law <98lawweijie@gmail.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Hans de Goede <hansg@kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: Guennadi Liakhovetski <guennadi.liakhovetski@linux.intel.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: [PATCH 2/2] media: uvcvideo: Fix out-of-bounds read in uvc_ctrl_status_event()
Date: Mon, 7 Sep 2026 14:28:18 +0800 [thread overview]
Message-ID: <20260907062819.2519878-3-98lawweijie@gmail.com> (raw)
In-Reply-To: <20260907062819.2519878-1-98lawweijie@gmail.com>
An out-of-bounds read exists in v6.12.105 and upstream. KASAN crash log:
BUG: KASAN: slab-use-after-free in uvc_get_le_value+0x314/0x350
Read of size 1 at addr ffff88802df955e4 by task kworker/0:2/128
Workqueue: events uvc_ctrl_status_event_work
uvc_ctrl_status_event+0x128/0x280
uvc_ctrl_status_event_work+0x82/0x240
The buggy address belongs to the object at ffff88802df955e0
which belongs to the cache kmalloc-16 of size 16
uvc_ctrl_add_mapping() validates mapping->offset against the control
data buffer, sized from the device's GET_LEN answer.
uvc_ctrl_status_event() applies the same offset to the 11 byte bValue
field of a control change event, so uvc_get_le_value() reads past the
16 byte struct uvc_status and the value is reported to userspace as a
V4L2_EVENT_CTRL change. offset is a u8 bit offset, so the read reaches
24 bytes into the neighbouring objects; KASAN calls it a use-after-free
because the neighbour it read had just been freed.
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
---
drivers/media/usb/uvc/uvc_ctrl.c | 13 +++++++++----
1 file changed, 9 insertions(+), 4 deletions(-)
diff --git a/drivers/media/usb/uvc/uvc_ctrl.c b/drivers/media/usb/uvc/uvc_ctrl.c
index 21802f9b1b61..d082bcb8d98d 100644
--- a/drivers/media/usb/uvc/uvc_ctrl.c
+++ b/drivers/media/usb/uvc/uvc_ctrl.c
@@ -2156,11 +2156,16 @@ void uvc_ctrl_status_event(struct uvc_video_chain *chain,
uvc_ctrl_clear_handle(ctrl);
list_for_each_entry(mapping, &ctrl->info.mappings, list) {
- s32 value;
+ s32 value = 0;
- if (uvc_ctrl_mapping_is_compound(mapping))
- value = 0;
- else
+ /*
+ * The offset is validated against the control size, not
+ * against the event payload, so a mapping can reach past
+ * bValue[].
+ */
+ if (!uvc_ctrl_mapping_is_compound(mapping) &&
+ mapping->offset + mapping->size <=
+ 8 * sizeof_field(struct uvc_status_control, bValue))
value = uvc_mapping_get_s32(mapping, UVC_GET_CUR, data);
/*
--
2.43.0
next prev parent reply other threads:[~2026-09-07 6:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 6:28 [PATCH 0/2] media: uvcvideo: Fix two bugs on the control change event path Wei Jie Law
2026-09-07 6:28 ` [PATCH 1/2] media: uvcvideo: Fix NULL deref on events for uninitialized controls Wei Jie Law
2026-09-07 7:00 ` Ricardo Ribalda
2026-09-07 8:12 ` Wei Jie LAW
2026-09-07 6:28 ` Wei Jie Law [this message]
2026-09-07 6:51 ` [PATCH 2/2] media: uvcvideo: Fix out-of-bounds read in uvc_ctrl_status_event() Ricardo Ribalda
2026-09-07 7:05 ` Wei Jie LAW
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=20260907062819.2519878-3-98lawweijie@gmail.com \
--to=98lawweijie@gmail.com \
--cc=guennadi.liakhovetski@linux.intel.com \
--cc=hansg@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.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