KASAN: vmalloc-out-of-bounds Write in tpg_fill_plane

Title	Replies (including bot)	Last reply
KASAN: vmalloc-out-of-bounds Write in tpg_fill_plane_buffer	0 (1)	2020/01/18 20:02

Title

Replies (including bot)

Last reply

KASAN: vmalloc-out-of-bounds Write in tpg_fill_plane_buffer

0 (1)

2020/01/18 20:02

Kernel	Title	Repro	Cause bisect	Fix bisect	Count	Last	Reported	Patched	Status
upstream	KASAN: vmalloc-out-of-bounds Write in tpg_fill_plane_buffer (3) media				7	9h03m	80d	0/28	upstream: reported on 2024/07/17 09:01
linux-5.15	KASAN: vmalloc-out-of-bounds Write in tpg_fill_plane_buffer				1	535d	535d	0/3	auto-obsoleted due to no activity on 2023/08/17 04:37
upstream	KASAN: vmalloc-out-of-bounds Write in tpg_fill_plane_buffer (2) media	C	inconclusive	done	14	614d	1125d	22/28	fixed on 2023/02/24 13:51

================================================================== BUG: KASAN: vmalloc-out-of-bounds in memcpy include/linux/string.h:380 [inline] BUG: KASAN: vmalloc-out-of-bounds in tpg_fill_plane_pattern drivers/media/common/v4l2-tpg/v4l2-tpg-core.c:2512 [inline] BUG: KASAN: vmalloc-out-of-bounds in tpg_fill_plane_buffer+0x10de/0x2f00 drivers/media/common/v4l2-tpg/v4l2-tpg-core.c:2600 Write of size 360 at addr ffffc90004e52ea0 by task vivid-000-vid-c/28265 CPU: 1 PID: 28265 Comm: vivid-000-vid-c Not tainted 5.5.0-rc6-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x197/0x210 lib/dump_stack.c:118 print_address_description.constprop.0.cold+0x5/0x30b mm/kasan/report.c:374 __kasan_report.cold+0x1b/0x41 mm/kasan/report.c:506 kasan_report+0x12/0x20 mm/kasan/common.c:639 check_memory_region_inline mm/kasan/generic.c:185 [inline] check_memory_region+0x134/0x1a0 mm/kasan/generic.c:192 memcpy+0x38/0x50 mm/kasan/common.c:126 memcpy include/linux/string.h:380 [inline] tpg_fill_plane_pattern drivers/media/common/v4l2-tpg/v4l2-tpg-core.c:2512 [inline] tpg_fill_plane_buffer+0x10de/0x2f00 drivers/media/common/v4l2-tpg/v4l2-tpg-core.c:2600 vivid_fillbuff+0x1861/0x3af0 drivers/media/platform/vivid/vivid-kthread-cap.c:468 vivid_thread_vid_cap_tick+0x8cf/0x2210 drivers/media/platform/vivid/vivid-kthread-cap.c:727 vivid_thread_vid_cap+0x5d8/0xa60 drivers/media/platform/vivid/vivid-kthread-cap.c:866 kthread+0x361/0x430 kernel/kthread.c:255 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:352 Memory state around the buggy address: ffffc90004e52f00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffffc90004e52f80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ffffc90004e53000: f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 ^ ffffc90004e53080: f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 ffffc90004e53100: f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 ==================================================================