* KASAN: slab-out-of-bounds Read in hid_field_extract
@ 2019-12-06 11:45 syzbot
2019-12-09 18:38 ` Alan Stern
0 siblings, 1 reply; 5+ messages in thread
From: syzbot @ 2019-12-06 11:45 UTC (permalink / raw)
To: andreyknvl, benjamin.tissoires, jikos, linux-input, linux-kernel,
linux-usb, syzkaller-bugs
Hello,
syzbot found the following crash on:
HEAD commit: 1f22d15c usb: gadget: add raw-gadget interface
git tree: https://github.com/google/kasan.git usb-fuzzer
console output: https://syzkaller.appspot.com/x/log.txt?x=11d12861e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=8ccee2968018adcb
dashboard link: https://syzkaller.appspot.com/bug?extid=09ef48aa58261464b621
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=101a781ee00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15d71c2ae00000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+09ef48aa58261464b621@syzkaller.appspotmail.com
==================================================================
BUG: KASAN: slab-out-of-bounds in __extract drivers/hid/hid-core.c:1345
[inline]
BUG: KASAN: slab-out-of-bounds in hid_field_extract+0x150/0x170
drivers/hid/hid-core.c:1365
Read of size 1 at addr ffff8881cf50f000 by task swapper/0/0
CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.4.0-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
<IRQ>
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0xef/0x16e lib/dump_stack.c:118
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:638
__extract drivers/hid/hid-core.c:1345 [inline]
hid_field_extract+0x150/0x170 drivers/hid/hid-core.c:1365
hid_input_field drivers/hid/hid-core.c:1537 [inline]
hid_report_raw_event+0x448/0xed0 drivers/hid/hid-core.c:1757
hid_input_report+0x315/0x3f0 drivers/hid/hid-core.c:1824
hid_irq_in+0x50e/0x690 drivers/hid/usbhid/hid-core.c:284
__usb_hcd_giveback_urb+0x1f2/0x470 drivers/usb/core/hcd.c:1648
usb_hcd_giveback_urb+0x368/0x420 drivers/usb/core/hcd.c:1713
dummy_timer+0x123d/0x2fdb drivers/usb/gadget/udc/dummy_hcd.c:1966
call_timer_fn+0x179/0x650 kernel/time/timer.c:1404
expire_timers kernel/time/timer.c:1449 [inline]
__run_timers kernel/time/timer.c:1773 [inline]
__run_timers kernel/time/timer.c:1740 [inline]
run_timer_softirq+0x5e3/0x1490 kernel/time/timer.c:1786
__do_softirq+0x221/0x912 kernel/softirq.c:292
invoke_softirq kernel/softirq.c:373 [inline]
irq_exit+0x178/0x1a0 kernel/softirq.c:413
exiting_irq arch/x86/include/asm/apic.h:536 [inline]
smp_apic_timer_interrupt+0x12f/0x500 arch/x86/kernel/apic/apic.c:1137
apic_timer_interrupt+0xf/0x20 arch/x86/entry/entry_64.S:829
</IRQ>
RIP: 0010:default_idle+0x28/0x2e0 arch/x86/kernel/process.c:700
Code: cc cc 41 56 41 55 65 44 8b 2d 1c e6 89 7a 41 54 55 53 0f 1f 44 00 00
e8 76 ed cb fb e9 07 00 00 00 0f 00 2d 2a 6c 4a 00 fb f4 <65> 44 8b 2d f8
e5 89 7a 0f 1f 44 00 00 5b 5d 41 5c 41 5d 41 5e c3
RSP: 0018:ffffffff86c07da8 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff13
RAX: 0000000000000007 RBX: ffffffff86c2b240 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000006 RDI: ffffffff86c2ba8c
RBP: fffffbfff0d85648 R08: ffffffff86c2b240 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
cpuidle_idle_call kernel/sched/idle.c:154 [inline]
do_idle+0x3c3/0x4e0 kernel/sched/idle.c:269
cpu_startup_entry+0x14/0x20 kernel/sched/idle.c:361
start_kernel+0x82a/0x864 init/main.c:784
secondary_startup_64+0xa4/0xb0 arch/x86/kernel/head_64.S:242
Allocated by task 12:
save_stack+0x1b/0x80 mm/kasan/common.c:71
set_track mm/kasan/common.c:79 [inline]
__kasan_kmalloc mm/kasan/common.c:512 [inline]
__kasan_kmalloc.constprop.0+0xbf/0xd0 mm/kasan/common.c:485
kmalloc include/linux/slab.h:561 [inline]
hcd_buffer_alloc+0x1ed/0x290 drivers/usb/core/buffer.c:132
usb_alloc_coherent+0x5d/0x80 drivers/usb/core/usb.c:910
hid_alloc_buffers drivers/hid/usbhid/hid-core.c:846 [inline]
usbhid_start+0x60b/0x22f0 drivers/hid/usbhid/hid-core.c:1075
hid_hw_start+0x5d/0x130 drivers/hid/hid-core.c:2022
ms_probe+0x159/0x4d0 drivers/hid/hid-microsoft.c:394
hid_device_probe+0x2be/0x3f0 drivers/hid/hid-core.c:2255
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+0x1480/0x1c20 drivers/base/core.c:2487
hid_add_device drivers/hid/hid-core.c:2411 [inline]
hid_add_device+0x33c/0x9a0 drivers/hid/hid-core.c:2360
usbhid_probe+0xa81/0xfa0 drivers/hid/usbhid/hid-core.c:1386
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+0x1480/0x1c20 drivers/base/core.c:2487
usb_set_configuration+0xe67/0x1740 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+0x1480/0x1c20 drivers/base/core.c:2487
usb_new_device.cold+0x6a4/0xe79 drivers/usb/core/hub.c:2537
hub_port_connect drivers/usb/core/hub.c:5184 [inline]
hub_port_connect_change drivers/usb/core/hub.c:5324 [inline]
port_event drivers/usb/core/hub.c:5470 [inline]
hub_event+0x1e59/0x3860 drivers/usb/core/hub.c:5552
process_one_work+0x92b/0x1530 kernel/workqueue.c:2264
worker_thread+0x96/0xe20 kernel/workqueue.c:2410
kthread+0x318/0x420 kernel/kthread.c:255
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:352
Freed by task 238:
save_stack+0x1b/0x80 mm/kasan/common.c:71
set_track mm/kasan/common.c:79 [inline]
kasan_set_free_info mm/kasan/common.c:334 [inline]
__kasan_slab_free+0x130/0x180 mm/kasan/common.c:473
slab_free_hook mm/slub.c:1425 [inline]
slab_free_freelist_hook mm/slub.c:1458 [inline]
slab_free mm/slub.c:3005 [inline]
kfree+0xdc/0x310 mm/slub.c:3957
uevent_show+0x2b9/0x360 drivers/base/core.c:1529
dev_attr_show+0x4b/0x90 drivers/base/core.c:1225
sysfs_kf_seq_show+0x1f8/0x410 fs/sysfs/file.c:60
seq_read+0x4b9/0x10f0 fs/seq_file.c:229
kernfs_fop_read+0xe9/0x560 fs/kernfs/file.c:251
__vfs_read+0x76/0x100 fs/read_write.c:425
vfs_read+0x1ea/0x430 fs/read_write.c:461
ksys_read+0x127/0x250 fs/read_write.c:587
do_syscall_64+0xb7/0x5b0 arch/x86/entry/common.c:294
entry_SYSCALL_64_after_hwframe+0x49/0xbe
The buggy address belongs to the object at ffff8881cf50e000
which belongs to the cache kmalloc-4k of size 4096
The buggy address is located 0 bytes to the right of
4096-byte region [ffff8881cf50e000, ffff8881cf50f000)
The buggy address belongs to the page:
page:ffffea00073d4200 refcount:1 mapcount:0 mapping:ffff8881da40c280
index:0x0 compound_mapcount: 0
raw: 0200000000010200 dead000000000100 dead000000000122 ffff8881da40c280
raw: 0000000000000000 0000000000040004 00000001ffffffff 0000000000000000
page dumped because: kasan: bad access detected
Memory state around the buggy address:
ffff8881cf50ef00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ffff8881cf50ef80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> ffff8881cf50f000: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
^
ffff8881cf50f080: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
ffff8881cf50f100: fc fc fc fc fc fc fc 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@googlegroups.com.
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: KASAN: slab-out-of-bounds Read in hid_field_extract
2019-12-06 11:45 KASAN: slab-out-of-bounds Read in hid_field_extract syzbot
@ 2019-12-09 18:38 ` Alan Stern
2019-12-09 19:12 ` syzbot
0 siblings, 1 reply; 5+ messages in thread
From: Alan Stern @ 2019-12-09 18:38 UTC (permalink / raw)
To: syzbot
Cc: andreyknvl, benjamin.tissoires, jikos, linux-input, linux-kernel,
linux-usb, syzkaller-bugs
On Fri, 6 Dec 2019, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit: 1f22d15c usb: gadget: add raw-gadget interface
> git tree: https://github.com/google/kasan.git usb-fuzzer
> console output: https://syzkaller.appspot.com/x/log.txt?x=11d12861e00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=8ccee2968018adcb
> dashboard link: https://syzkaller.appspot.com/bug?extid=09ef48aa58261464b621
> compiler: gcc (GCC) 9.0.0 20181231 (experimental)
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=101a781ee00000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15d71c2ae00000
>
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: syzbot+09ef48aa58261464b621@syzkaller.appspotmail.com
>
> ==================================================================
> BUG: KASAN: slab-out-of-bounds in __extract drivers/hid/hid-core.c:1345
> [inline]
> BUG: KASAN: slab-out-of-bounds in hid_field_extract+0x150/0x170
> drivers/hid/hid-core.c:1365
> Read of size 1 at addr ffff8881cf50f000 by task swapper/0/0
Diagnostic patch.
#syz test: https://github.com/google/kasan.git 1f22d15c
Index: usb-devel/drivers/hid/hid-core.c
===================================================================
--- usb-devel.orig/drivers/hid/hid-core.c
+++ usb-devel/drivers/hid/hid-core.c
@@ -1488,6 +1488,7 @@ static void hid_input_field(struct hid_d
if (!value)
return;
+ hid_info(hid, "Field offset %u size %u count %u\n", offset, size, count);
for (n = 0; n < count; n++) {
value[n] = min < 0 ?
@@ -1712,6 +1713,7 @@ int hid_report_raw_event(struct hid_devi
}
if (hid->claimed != HID_CLAIMED_HIDRAW && report->maxfield) {
+ hid_info(hid, "Report rsize %u csize %u\n", rsize, csize);
for (a = 0; a < report->maxfield; a++)
hid_input_field(hid, report->field[a], cdata, interrupt);
hdrv = hid->driver;
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: KASAN: slab-out-of-bounds Read in hid_field_extract
2019-12-09 18:38 ` Alan Stern
@ 2019-12-09 19:12 ` syzbot
2019-12-09 19:51 ` Alan Stern
0 siblings, 1 reply; 5+ messages in thread
From: syzbot @ 2019-12-09 19:12 UTC (permalink / raw)
To: andreyknvl, benjamin.tissoires, jikos, linux-input, linux-kernel,
linux-usb, stern, syzkaller-bugs
Hello,
syzbot has tested the proposed patch but the reproducer still triggered
crash:
KASAN: slab-out-of-bounds Read in hid_field_extract
microsoft 0003:045E:07DA.0001: Report rsize 4096 csize 1
microsoft 0003:045E:07DA.0001: Field offset 0 size 12 count 4899
==================================================================
BUG: KASAN: slab-out-of-bounds in __extract drivers/hid/hid-core.c:1345
[inline]
BUG: KASAN: slab-out-of-bounds in hid_field_extract+0x150/0x170
drivers/hid/hid-core.c:1365
Read of size 1 at addr ffff8881cc759000 by task swapper/1/0
CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.4.0-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
<IRQ>
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0xef/0x16e lib/dump_stack.c:118
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:638
__extract drivers/hid/hid-core.c:1345 [inline]
hid_field_extract+0x150/0x170 drivers/hid/hid-core.c:1365
hid_input_field drivers/hid/hid-core.c:1538 [inline]
hid_report_raw_event.cold+0x6c9/0xbad drivers/hid/hid-core.c:1759
hid_input_report+0x315/0x3f0 drivers/hid/hid-core.c:1826
hid_irq_in+0x50e/0x690 drivers/hid/usbhid/hid-core.c:284
__usb_hcd_giveback_urb+0x1f2/0x470 drivers/usb/core/hcd.c:1648
usb_hcd_giveback_urb+0x368/0x420 drivers/usb/core/hcd.c:1713
dummy_timer+0x123d/0x2fdb drivers/usb/gadget/udc/dummy_hcd.c:1966
call_timer_fn+0x179/0x650 kernel/time/timer.c:1404
expire_timers kernel/time/timer.c:1449 [inline]
__run_timers kernel/time/timer.c:1773 [inline]
__run_timers kernel/time/timer.c:1740 [inline]
run_timer_softirq+0x5e3/0x1490 kernel/time/timer.c:1786
__do_softirq+0x221/0x912 kernel/softirq.c:292
invoke_softirq kernel/softirq.c:373 [inline]
irq_exit+0x178/0x1a0 kernel/softirq.c:413
exiting_irq arch/x86/include/asm/apic.h:536 [inline]
smp_apic_timer_interrupt+0x12f/0x500 arch/x86/kernel/apic/apic.c:1137
apic_timer_interrupt+0xf/0x20 arch/x86/entry/entry_64.S:829
</IRQ>
RIP: 0010:default_idle+0x28/0x2e0 arch/x86/kernel/process.c:700
Code: cc cc 41 56 41 55 65 44 8b 2d 1c e6 89 7a 41 54 55 53 0f 1f 44 00 00
e8 76 ed cb fb e9 07 00 00 00 0f 00 2d 2a 6c 4a 00 fb f4 <65> 44 8b 2d f8
e5 89 7a 0f 1f 44 00 00 5b 5d 41 5c 41 5d 41 5e c3
RSP: 0018:ffff8881da62fdc8 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff13
RAX: 0000000000000007 RBX: ffff8881da613100 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000006 RDI: ffff8881da61394c
RBP: ffffed103b4c2620 R08: ffff8881da613100 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001
R13: 0000000000000001 R14: 0000000000000000 R15: 0000000000000000
cpuidle_idle_call kernel/sched/idle.c:154 [inline]
do_idle+0x3c3/0x4e0 kernel/sched/idle.c:269
cpu_startup_entry+0x14/0x20 kernel/sched/idle.c:361
start_secondary+0x27d/0x330 arch/x86/kernel/smpboot.c:264
secondary_startup_64+0xa4/0xb0 arch/x86/kernel/head_64.S:242
Allocated by task 17:
save_stack+0x1b/0x80 mm/kasan/common.c:71
set_track mm/kasan/common.c:79 [inline]
__kasan_kmalloc mm/kasan/common.c:512 [inline]
__kasan_kmalloc.constprop.0+0xbf/0xd0 mm/kasan/common.c:485
kmalloc include/linux/slab.h:561 [inline]
hcd_buffer_alloc+0x1ed/0x290 drivers/usb/core/buffer.c:132
usb_alloc_coherent+0x5d/0x80 drivers/usb/core/usb.c:910
hid_alloc_buffers drivers/hid/usbhid/hid-core.c:846 [inline]
usbhid_start+0x60b/0x22f0 drivers/hid/usbhid/hid-core.c:1075
hid_hw_start+0x5d/0x130 drivers/hid/hid-core.c:2024
ms_probe+0x159/0x4d0 drivers/hid/hid-microsoft.c:394
hid_device_probe+0x2be/0x3f0 drivers/hid/hid-core.c:2257
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+0x1480/0x1c20 drivers/base/core.c:2487
hid_add_device drivers/hid/hid-core.c:2413 [inline]
hid_add_device+0x33c/0x9a0 drivers/hid/hid-core.c:2362
usbhid_probe+0xa81/0xfa0 drivers/hid/usbhid/hid-core.c:1386
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+0x1480/0x1c20 drivers/base/core.c:2487
usb_set_configuration+0xe67/0x1740 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+0x1480/0x1c20 drivers/base/core.c:2487
usb_new_device.cold+0x6a4/0xe79 drivers/usb/core/hub.c:2537
hub_port_connect drivers/usb/core/hub.c:5184 [inline]
hub_port_connect_change drivers/usb/core/hub.c:5324 [inline]
port_event drivers/usb/core/hub.c:5470 [inline]
hub_event+0x1e59/0x3860 drivers/usb/core/hub.c:5552
process_one_work+0x92b/0x1530 kernel/workqueue.c:2264
worker_thread+0x96/0xe20 kernel/workqueue.c:2410
kthread+0x318/0x420 kernel/kthread.c:255
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:352
Freed by task 0:
(stack is not available)
The buggy address belongs to the object at ffff8881cc758000
which belongs to the cache kmalloc-4k of size 4096
The buggy address is located 0 bytes to the right of
4096-byte region [ffff8881cc758000, ffff8881cc759000)
The buggy address belongs to the page:
page:ffffea000731d600 refcount:1 mapcount:0 mapping:ffff8881da40c280
index:0x0 compound_mapcount: 0
raw: 0200000000010200 dead000000000100 dead000000000122 ffff8881da40c280
raw: 0000000000000000 0000000000040004 00000001ffffffff 0000000000000000
page dumped because: kasan: bad access detected
Memory state around the buggy address:
ffff8881cc758f00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ffff8881cc758f80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> ffff8881cc759000: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
^
ffff8881cc759080: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
ffff8881cc759100: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
==================================================================
Tested on:
commit: 1f22d15c usb: gadget: add raw-gadget interface
git tree: https://github.com/google/kasan.git
console output: https://syzkaller.appspot.com/x/log.txt?x=13b9f446e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=8ccee2968018adcb
dashboard link: https://syzkaller.appspot.com/bug?extid=09ef48aa58261464b621
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
patch: https://syzkaller.appspot.com/x/patch.diff?x=137641dae00000
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: KASAN: slab-out-of-bounds Read in hid_field_extract
2019-12-09 19:12 ` syzbot
@ 2019-12-09 19:51 ` Alan Stern
2019-12-09 23:46 ` syzbot
0 siblings, 1 reply; 5+ messages in thread
From: Alan Stern @ 2019-12-09 19:51 UTC (permalink / raw)
To: syzbot
Cc: andreyknvl, benjamin.tissoires, jikos, linux-input, linux-kernel,
linux-usb, syzkaller-bugs
On Mon, 9 Dec 2019, syzbot wrote:
> Hello,
>
> syzbot has tested the proposed patch but the reproducer still triggered
> crash:
> KASAN: slab-out-of-bounds Read in hid_field_extract
>
> microsoft 0003:045E:07DA.0001: Report rsize 4096 csize 1
> microsoft 0003:045E:07DA.0001: Field offset 0 size 12 count 4899
> ==================================================================
> BUG: KASAN: slab-out-of-bounds in __extract drivers/hid/hid-core.c:1345
> [inline]
> BUG: KASAN: slab-out-of-bounds in hid_field_extract+0x150/0x170
> drivers/hid/hid-core.c:1365
> Read of size 1 at addr ffff8881cc759000 by task swapper/1/0
Nobody bothers to check for ridiculously long reports? This field had
report_size = 12 and report_count = 4899!
Alan Stern
#syz test: https://github.com/google/kasan.git 1f22d15c
Index: usb-devel/drivers/hid/hid-core.c
===================================================================
--- usb-devel.orig/drivers/hid/hid-core.c
+++ usb-devel/drivers/hid/hid-core.c
@@ -267,6 +267,10 @@ static int hid_add_field(struct hid_pars
offset = report->size;
report->size += parser->global.report_size * parser->global.report_count;
+ if (report->size > HID_MAX_BUFFER_SIZE << 3) {
+ hid_err(parser->device, "report is too long\n");
+ return -1;
+ }
if (!parser->local.usage_index) /* Ignore padding fields */
return 0;
@@ -1488,6 +1492,7 @@ static void hid_input_field(struct hid_d
if (!value)
return;
+ hid_info(hid, "Field offset %u size %u count %u\n", offset, size, count);
for (n = 0; n < count; n++) {
value[n] = min < 0 ?
@@ -1712,6 +1717,7 @@ int hid_report_raw_event(struct hid_devi
}
if (hid->claimed != HID_CLAIMED_HIDRAW && report->maxfield) {
+ hid_info(hid, "Report rsize %u csize %u\n", rsize, csize);
for (a = 0; a < report->maxfield; a++)
hid_input_field(hid, report->field[a], cdata, interrupt);
hdrv = hid->driver;
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: KASAN: slab-out-of-bounds Read in hid_field_extract
2019-12-09 19:51 ` Alan Stern
@ 2019-12-09 23:46 ` syzbot
0 siblings, 0 replies; 5+ messages in thread
From: syzbot @ 2019-12-09 23:46 UTC (permalink / raw)
To: andreyknvl, benjamin.tissoires, jikos, linux-input, linux-kernel,
linux-usb, stern, syzkaller-bugs
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger
crash:
Reported-and-tested-by:
syzbot+09ef48aa58261464b621@syzkaller.appspotmail.com
Tested on:
commit: 1f22d15c usb: gadget: add raw-gadget interface
git tree: https://github.com/google/kasan.git
kernel config: https://syzkaller.appspot.com/x/.config?x=8ccee2968018adcb
dashboard link: https://syzkaller.appspot.com/bug?extid=09ef48aa58261464b621
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
patch: https://syzkaller.appspot.com/x/patch.diff?x=146cae41e00000
Note: testing is done by a robot and is best-effort only.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2019-12-09 23:46 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-12-06 11:45 KASAN: slab-out-of-bounds Read in hid_field_extract syzbot
2019-12-09 18:38 ` Alan Stern
2019-12-09 19:12 ` syzbot
2019-12-09 19:51 ` Alan Stern
2019-12-09 23:46 ` syzbot
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).