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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:   Sat, 18 Jan 2020 12:02:10 -0800
From:   syzbot <syzbot+698def9813b5d6596933@...kaller.appspotmail.com>
To:     hverkuil-cisco@...all.nl, linux-kernel@...r.kernel.org,
        linux-media@...r.kernel.org, mchehab@...nel.org,
        syzkaller-bugs@...glegroups.com, vivek.kasireddy@...el.com
Subject: KASAN: vmalloc-out-of-bounds Write in tpg_fill_plane_buffer

Hello,

syzbot found the following crash on:

HEAD commit:    25e73aad Merge tag 'io_uring-5.5-2020-01-16' of git://git...
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1684f959e00000
kernel config:  https://syzkaller.appspot.com/x/.config?x=d9290aeb7e6cf1c4
dashboard link: https://syzkaller.appspot.com/bug?extid=698def9813b5d6596933
compiler:       gcc (GCC) 9.0.0 20181231 (experimental)

Unfortunately, I don't have any reproducer for this crash yet.

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+698def9813b5d6596933@...kaller.appspotmail.com

==================================================================
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
==================================================================


---
This bug is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@...glegroups.com.

syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.