KASAN: slab-out-of-bounds Read in parse_term_proc_unit

From: syzbot
Date: Tue Oct 22 2019 - 20:15:13 EST

Next message: Rajat Jain: "Re: New sysfs interface for privacy screens"
Previous message: Rajat Jain: "[PATCH] drm: Add support for integrated privacy screens"
Next in thread: Takashi Iwai: "Re: [alsa-devel] KASAN: slab-out-of-bounds Read in parse_term_proc_unit"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hello,

syzbot found the following crash on:

HEAD commit: 22be26f7 usb-fuzzer: main usb gadget fuzzer driver
git tree: https://github.com/google/kasan.git usb-fuzzer
console output: https://syzkaller.appspot.com/x/log.txt?x=141c4097600000
kernel config: https://syzkaller.appspot.com/x/.config?x=387eccb7ac68ec5
dashboard link: https://syzkaller.appspot.com/bug?extid=f586a582f79122007598
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=169fe2df600000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13e2f3ef600000

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+f586a582f79122007598@xxxxxxxxxxxxxxxxxxxxxxxxx

usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-1: Product: syz
usb 1-1: Manufacturer: syz
usb 1-1: SerialNumber: syz
==================================================================
BUG: KASAN: slab-out-of-bounds in uac_processing_unit_iProcessing include/uapi/linux/usb/audio.h:429 [inline]
BUG: KASAN: slab-out-of-bounds in parse_term_proc_unit+0x57a/0x5e0 sound/usb/mixer.c:896
Read of size 1 at addr ffff8881d48eeca9 by task kworker/1:2/83

CPU: 1 PID: 83 Comm: kworker/1:2 Not tainted 5.4.0-rc3+ #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: usb_hub_wq hub_event
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0xca/0x13e lib/dump_stack.c:113
print_address_description.constprop.0+0x36/0x50 mm/kasan/report.c:374
__kasan_report.cold+0x1a/0x33 mm/kasan/report.c:506
kasan_report+0xe/0x20 mm/kasan/common.c:634
uac_processing_unit_iProcessing include/uapi/linux/usb/audio.h:429 [inline]
parse_term_proc_unit+0x57a/0x5e0 sound/usb/mixer.c:896
__check_input_term+0xc32/0x13f0 sound/usb/mixer.c:984
parse_audio_feature_unit sound/usb/mixer.c:1875 [inline]
parse_audio_unit+0x101d/0x36f0 sound/usb/mixer.c:2753
snd_usb_mixer_controls+0x715/0xb90 sound/usb/mixer.c:3095
snd_usb_create_mixer+0x2b5/0x1890 sound/usb/mixer.c:3445
usb_audio_probe+0xc76/0x2010 sound/usb/card.c:653
usb_probe_interface+0x305/0x7a0 drivers/usb/core/driver.c:361
really_probe+0x281/0x6d0 drivers/base/dd.c:548
driver_probe_device+0x104/0x210 drivers/base/dd.c:721
__device_attach_driver+0x1c2/0x220 drivers/base/dd.c:828
bus_for_each_drv+0x162/0x1e0 drivers/base/bus.c:430
__device_attach+0x217/0x360 drivers/base/dd.c:894
bus_probe_device+0x1e4/0x290 drivers/base/bus.c:490
device_add+0xae6/0x16f0 drivers/base/core.c:2201
usb_set_configuration+0xdf6/0x1670 drivers/usb/core/message.c:2023
generic_probe+0x9d/0xd5 drivers/usb/core/generic.c:210
usb_probe_device+0x99/0x100 drivers/usb/core/driver.c:266
really_probe+0x281/0x6d0 drivers/base/dd.c:548
driver_probe_device+0x104/0x210 drivers/base/dd.c:721
__device_attach_driver+0x1c2/0x220 drivers/base/dd.c:828
bus_for_each_drv+0x162/0x1e0 drivers/base/bus.c:430
__device_attach+0x217/0x360 drivers/base/dd.c:894
bus_probe_device+0x1e4/0x290 drivers/base/bus.c:490
device_add+0xae6/0x16f0 drivers/base/core.c:2201
usb_new_device.cold+0x6a4/0xe79 drivers/usb/core/hub.c:2536
hub_port_connect drivers/usb/core/hub.c:5183 [inline]
hub_port_connect_change drivers/usb/core/hub.c:5323 [inline]
port_event drivers/usb/core/hub.c:5469 [inline]
hub_event+0x1dd0/0x37e0 drivers/usb/core/hub.c:5551
process_one_work+0x92b/0x1530 kernel/workqueue.c:2269
worker_thread+0x96/0xe20 kernel/workqueue.c:2415
kthread+0x318/0x420 kernel/kthread.c:255
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:352

Allocated by task 83:
save_stack+0x1b/0x80 mm/kasan/common.c:69
set_track mm/kasan/common.c:77 [inline]
__kasan_kmalloc mm/kasan/common.c:510 [inline]
__kasan_kmalloc.constprop.0+0xbf/0xd0 mm/kasan/common.c:483
kmalloc include/linux/slab.h:561 [inline]
usb_get_configuration+0x314/0x3050 drivers/usb/core/config.c:857
usb_enumerate_device drivers/usb/core/hub.c:2369 [inline]
usb_new_device+0xd3/0x160 drivers/usb/core/hub.c:2505
hub_port_connect drivers/usb/core/hub.c:5183 [inline]
hub_port_connect_change drivers/usb/core/hub.c:5323 [inline]
port_event drivers/usb/core/hub.c:5469 [inline]
hub_event+0x1dd0/0x37e0 drivers/usb/core/hub.c:5551
process_one_work+0x92b/0x1530 kernel/workqueue.c:2269
worker_thread+0x96/0xe20 kernel/workqueue.c:2415
kthread+0x318/0x420 kernel/kthread.c:255
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:352

Freed by task 0:
save_stack+0x1b/0x80 mm/kasan/common.c:69
set_track mm/kasan/common.c:77 [inline]
kasan_set_free_info mm/kasan/common.c:332 [inline]
__kasan_slab_free+0x130/0x180 mm/kasan/common.c:471
slab_free_hook mm/slub.c:1424 [inline]
slab_free_freelist_hook mm/slub.c:1475 [inline]
slab_free mm/slub.c:3018 [inline]
kfree+0xe4/0x320 mm/slub.c:3967
free_task+0xe3/0x110 kernel/fork.c:472
__put_task_struct+0x1e2/0x4c0 kernel/fork.c:748
put_task_struct include/linux/sched/task.h:119 [inline]
delayed_put_task_struct+0x1b4/0x2c0 kernel/exit.c:182
__rcu_reclaim kernel/rcu/rcu.h:222 [inline]
rcu_do_batch kernel/rcu/tree.c:2157 [inline]
rcu_core+0x630/0x1ca0 kernel/rcu/tree.c:2377
__do_softirq+0x221/0x912 kernel/softirq.c:292

The buggy address belongs to the object at ffff8881d48eec00
which belongs to the cache kmalloc-192 of size 192
The buggy address is located 169 bytes inside of
192-byte region [ffff8881d48eec00, ffff8881d48eecc0)
The buggy address belongs to the page:
page:ffffea0007523b80 refcount:1 mapcount:0 mapping:ffff8881da002a00 index:0x0
flags: 0x200000000000200(slab)
raw: 0200000000000200 ffffea000753ce40 0000000e0000000e ffff8881da002a00
raw: 0000000000000000 0000000000100010 00000001ffffffff 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
ffff8881d48eeb80: fb fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc
ffff8881d48eec00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

ffff8881d48eec80: 00 00 00 00 03 fc fc fc fc fc fc fc fc fc fc fc

^
ffff8881d48eed00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ffff8881d48eed80: 00 00 00 00 00 00 00 fc fc fc fc fc fc fc fc fc
==================================================================

---
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@xxxxxxxxxxxxxxxxx

syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this bug, for details see:
https://goo.gl/tpsmEJ#testing-patches

Next message: Rajat Jain: "Re: New sysfs interface for privacy screens"
Previous message: Rajat Jain: "[PATCH] drm: Add support for integrated privacy screens"
Next in thread: Takashi Iwai: "Re: [alsa-devel] KASAN: slab-out-of-bounds Read in parse_term_proc_unit"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]