KASAN: use-after-free Read in ntfs_attr_find
11 views
Skip to first unread message
syzbot
Sep 23, 2020, 7:31:15 AM9/23/20
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: cbfa1702 Linux 4.14.198
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16fc4b07900000
kernel config: https://syzkaller.appspot.com/x/.config?x=3990958d85b55e59
dashboard link: https://syzkaller.appspot.com/bug?extid=31f564ac63c1fb454df9
compiler: gcc (GCC) 10.1.0-syz 20200507
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+31f564...@syzkaller.appspotmail.com
==================================================================
BUG: KASAN: use-after-free in ntfs_attr_find+0x8df/0xa10 fs/ntfs/attrib.c:613
Read of size 4 at addr ffff8880561562c0 by task syz-executor.1/23367
CPU: 0 PID: 23367 Comm: syz-executor.1 Not tainted 4.14.198-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x283 lib/dump_stack.c:58
print_address_description.cold+0x54/0x1d3 mm/kasan/report.c:252
kasan_report_error.cold+0x8a/0x194 mm/kasan/report.c:351
kasan_report mm/kasan/report.c:409 [inline]
__asan_report_load_n_noabort+0x6b/0x80 mm/kasan/report.c:440
ntfs_attr_find+0x8df/0xa10 fs/ntfs/attrib.c:613
ntfs_attr_lookup+0xeca/0x1f30 fs/ntfs/attrib.c:1203
ntfs_read_inode_mount+0x6b4/0x1fb0 fs/ntfs/inode.c:1867
ntfs_fill_super+0x9a6/0x7170 fs/ntfs/super.c:2871
mount_bdev+0x2b3/0x360 fs/super.c:1134
mount_fs+0x92/0x2a0 fs/super.c:1237
vfs_kern_mount.part.0+0x5b/0x470 fs/namespace.c:1046
vfs_kern_mount fs/namespace.c:1036 [inline]
do_new_mount fs/namespace.c:2549 [inline]
do_mount+0xe53/0x2a00 fs/namespace.c:2879
SYSC_mount fs/namespace.c:3095 [inline]
SyS_mount+0xa8/0x120 fs/namespace.c:3072
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x460bca
RSP: 002b:00007fde5e67ca88 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007fde5e67cb20 RCX: 0000000000460bca
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007fde5e67cae0
RBP: 00007fde5e67cae0 R08: 00007fde5e67cb20 R09: 0000000020000000
R10: 0000000000000000 R11: 0000000000000202 R12: 0000000020000000
R13: 0000000020000100 R14: 0000000020000200 R15: 000000002007dc00
Allocated by task 22978:
save_stack mm/kasan/kasan.c:447 [inline]
set_track mm/kasan/kasan.c:459 [inline]
kasan_kmalloc+0xeb/0x160 mm/kasan/kasan.c:551
kmem_cache_alloc_node+0x146/0x410 mm/slab.c:3642
alloc_task_struct_node kernel/fork.c:156 [inline]
dup_task_struct kernel/fork.c:515 [inline]
copy_process.part.0+0x17db/0x6f00 kernel/fork.c:1611
copy_process kernel/fork.c:1586 [inline]
_do_fork+0x184/0xc80 kernel/fork.c:2070
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
Freed by task 6368:
save_stack mm/kasan/kasan.c:447 [inline]
set_track mm/kasan/kasan.c:459 [inline]
kasan_slab_free+0xc3/0x1a0 mm/kasan/kasan.c:524
__cache_free mm/slab.c:3496 [inline]
kmem_cache_free+0x7c/0x2b0 mm/slab.c:3758
__put_task_struct+0x276/0x470 kernel/fork.c:420
put_task_struct include/linux/sched/task.h:98 [inline]
delayed_put_task_struct+0x1fb/0x2e0 kernel/exit.c:180
__rcu_reclaim kernel/rcu/rcu.h:195 [inline]
rcu_do_batch kernel/rcu/tree.c:2699 [inline]
invoke_rcu_callbacks kernel/rcu/tree.c:2962 [inline]
__rcu_process_callbacks kernel/rcu/tree.c:2929 [inline]
rcu_process_callbacks+0x780/0x1180 kernel/rcu/tree.c:2946
__do_softirq+0x254/0xa1d kernel/softirq.c:288
The buggy address belongs to the object at ffff888056156100
which belongs to the cache task_struct of size 6144
The buggy address is located 448 bytes inside of
6144-byte region [ffff888056156100, ffff888056157900)
The buggy address belongs to the page:
page:ffffea0001585580 count:1 mapcount:0 mapping:ffff888056156100 index:0x0 compound_mapcount: 0
flags: 0xfffe0000008100(slab|head)
raw: 00fffe0000008100 ffff888056156100 0000000000000000 0000000100000001
raw: ffffea0002a4fa20 ffffea00014ddea0 ffff88821f8307c0 0000000000000000
page dumped because: kasan: bad access detected
Memory state around the buggy address:
ffff888056156180: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
ffff888056156200: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
>ffff888056156280: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
^
ffff888056156300: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
ffff888056156380: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
==================================================================
---
This report 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 syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot found the following issue on:
HEAD commit: cbfa1702 Linux 4.14.198
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16fc4b07900000
kernel config: https://syzkaller.appspot.com/x/.config?x=3990958d85b55e59
dashboard link: https://syzkaller.appspot.com/bug?extid=31f564ac63c1fb454df9
compiler: gcc (GCC) 10.1.0-syz 20200507
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+31f564...@syzkaller.appspotmail.com
==================================================================
BUG: KASAN: use-after-free in ntfs_attr_find+0x8df/0xa10 fs/ntfs/attrib.c:613
Read of size 4 at addr ffff8880561562c0 by task syz-executor.1/23367
CPU: 0 PID: 23367 Comm: syz-executor.1 Not tainted 4.14.198-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x283 lib/dump_stack.c:58
print_address_description.cold+0x54/0x1d3 mm/kasan/report.c:252
kasan_report_error.cold+0x8a/0x194 mm/kasan/report.c:351
kasan_report mm/kasan/report.c:409 [inline]
__asan_report_load_n_noabort+0x6b/0x80 mm/kasan/report.c:440
ntfs_attr_find+0x8df/0xa10 fs/ntfs/attrib.c:613
ntfs_attr_lookup+0xeca/0x1f30 fs/ntfs/attrib.c:1203
ntfs_read_inode_mount+0x6b4/0x1fb0 fs/ntfs/inode.c:1867
ntfs_fill_super+0x9a6/0x7170 fs/ntfs/super.c:2871
mount_bdev+0x2b3/0x360 fs/super.c:1134
mount_fs+0x92/0x2a0 fs/super.c:1237
vfs_kern_mount.part.0+0x5b/0x470 fs/namespace.c:1046
vfs_kern_mount fs/namespace.c:1036 [inline]
do_new_mount fs/namespace.c:2549 [inline]
do_mount+0xe53/0x2a00 fs/namespace.c:2879
SYSC_mount fs/namespace.c:3095 [inline]
SyS_mount+0xa8/0x120 fs/namespace.c:3072
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x460bca
RSP: 002b:00007fde5e67ca88 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007fde5e67cb20 RCX: 0000000000460bca
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007fde5e67cae0
RBP: 00007fde5e67cae0 R08: 00007fde5e67cb20 R09: 0000000020000000
R10: 0000000000000000 R11: 0000000000000202 R12: 0000000020000000
R13: 0000000020000100 R14: 0000000020000200 R15: 000000002007dc00
Allocated by task 22978:
save_stack mm/kasan/kasan.c:447 [inline]
set_track mm/kasan/kasan.c:459 [inline]
kasan_kmalloc+0xeb/0x160 mm/kasan/kasan.c:551
kmem_cache_alloc_node+0x146/0x410 mm/slab.c:3642
alloc_task_struct_node kernel/fork.c:156 [inline]
dup_task_struct kernel/fork.c:515 [inline]
copy_process.part.0+0x17db/0x6f00 kernel/fork.c:1611
copy_process kernel/fork.c:1586 [inline]
_do_fork+0x184/0xc80 kernel/fork.c:2070
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
Freed by task 6368:
save_stack mm/kasan/kasan.c:447 [inline]
set_track mm/kasan/kasan.c:459 [inline]
kasan_slab_free+0xc3/0x1a0 mm/kasan/kasan.c:524
__cache_free mm/slab.c:3496 [inline]
kmem_cache_free+0x7c/0x2b0 mm/slab.c:3758
__put_task_struct+0x276/0x470 kernel/fork.c:420
put_task_struct include/linux/sched/task.h:98 [inline]
delayed_put_task_struct+0x1fb/0x2e0 kernel/exit.c:180
__rcu_reclaim kernel/rcu/rcu.h:195 [inline]
rcu_do_batch kernel/rcu/tree.c:2699 [inline]
invoke_rcu_callbacks kernel/rcu/tree.c:2962 [inline]
__rcu_process_callbacks kernel/rcu/tree.c:2929 [inline]
rcu_process_callbacks+0x780/0x1180 kernel/rcu/tree.c:2946
__do_softirq+0x254/0xa1d kernel/softirq.c:288
The buggy address belongs to the object at ffff888056156100
which belongs to the cache task_struct of size 6144
The buggy address is located 448 bytes inside of
6144-byte region [ffff888056156100, ffff888056157900)
The buggy address belongs to the page:
page:ffffea0001585580 count:1 mapcount:0 mapping:ffff888056156100 index:0x0 compound_mapcount: 0
flags: 0xfffe0000008100(slab|head)
raw: 00fffe0000008100 ffff888056156100 0000000000000000 0000000100000001
raw: ffffea0002a4fa20 ffffea00014ddea0 ffff88821f8307c0 0000000000000000
page dumped because: kasan: bad access detected
Memory state around the buggy address:
ffff888056156180: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
ffff888056156200: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
>ffff888056156280: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
^
ffff888056156300: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
ffff888056156380: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
==================================================================
---
This report 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 syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot
Sep 26, 2020, 9:02:17 PM9/26/20
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 10ad6cfd Linux 4.19.148
syzbot found the following issue on:
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14bc2f9b900000
kernel config: https://syzkaller.appspot.com/x/.config?x=ef9a7978d84ee42b
dashboard link: https://syzkaller.appspot.com/bug?extid=3d4253be2382d1e54450
compiler: gcc (GCC) 10.1.0-syz 20200507
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+3d4253...@syzkaller.appspotmail.com
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
BTRFS error (device loop2): unsupported checksum algorithm 3
(syz-executor.3,1420,1):ocfs2_parse_options:1513 ERROR: Invalid heartbeat mount options
BTRFS error (device loop2): superblock checksum mismatch
==================================================================
BUG: KASAN: use-after-free in ntfs_attr_find+0xa42/0xb70 fs/ntfs/attrib.c:613
Read of size 4 at addr ffff88809a778c3f by task syz-executor.1/1418
CPU: 1 PID: 1418 Comm: syz-executor.1 Not tainted 4.19.148-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]
Call Trace:
dump_stack+0x22c/0x33e lib/dump_stack.c:118
print_address_description.cold+0x56/0x25c mm/kasan/report.c:256
kasan_report_error.cold+0x66/0xb9 mm/kasan/report.c:354
kasan_report mm/kasan/report.c:412 [inline]
__asan_report_load_n_noabort+0x8b/0xa0 mm/kasan/report.c:443
ntfs_attr_find+0xa42/0xb70 fs/ntfs/attrib.c:613
ntfs_attr_lookup+0x1087/0x2060 fs/ntfs/attrib.c:1203
ntfs_read_inode_mount+0x7e4/0x23b0 fs/ntfs/inode.c:1858
ntfs_fill_super+0x1761/0x89d2 fs/ntfs/super.c:2871
mount_bdev+0x2fc/0x3b0 fs/super.c:1158
mount_fs+0xa3/0x318 fs/super.c:1261
vfs_kern_mount.part.0+0x68/0x470 fs/namespace.c:961
vfs_kern_mount fs/namespace.c:951 [inline]
do_new_mount fs/namespace.c:2469 [inline]
do_mount+0x51c/0x2f10 fs/namespace.c:2799
ksys_mount+0xcf/0x130 fs/namespace.c:3015
__do_sys_mount fs/namespace.c:3029 [inline]
__se_sys_mount fs/namespace.c:3026 [inline]
__x64_sys_mount+0xba/0x150 fs/namespace.c:3026
do_syscall_64+0xf9/0x670 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x460bca
Code: b8 a6 00 00 00 0f 05 48 3d 01 f0 ff ff 0f 83 dd 87 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 0f 83 ba 87 fb ff c3 66 0f 1f 84 00 00 00 00 00
RSP: 002b:00007f9188ed6a88 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f9188ed6b20 RCX: 0000000000460bca
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007f9188ed6ae0
RBP: 00007f9188ed6ae0 R08: 00007f9188ed6b20 R09: 0000000020000000
R10: 0000000000000000 R11: 0000000000000202 R12: 0000000020000000
R13: 0000000020000100 R14: 0000000020000200 R15: 0000000020099000
Allocated by task 3717:
kmem_cache_alloc+0x126/0x4a0 mm/slab.c:3559
getname_flags+0xce/0x590 fs/namei.c:140
do_sys_open+0x26c/0x520 fs/open.c:1079
do_syscall_64+0xf9/0x670 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
Freed by task 3717:
__cache_free mm/slab.c:3503 [inline]
kmem_cache_free+0x7f/0x2b0 mm/slab.c:3765
putname+0xe1/0x130 fs/namei.c:261
do_sys_open+0x2ba/0x520 fs/open.c:1094
do_syscall_64+0xf9/0x670 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
The buggy address belongs to the object at ffff88809a7788c0
which belongs to the cache names_cache of size 4096
The buggy address is located 895 bytes inside of
4096-byte region [ffff88809a7788c0, ffff88809a7798c0)
The buggy address belongs to the page:
page:ffffea000269de00 count:1 mapcount:0 mapping:ffff88821bc44b00 index:0x0 compound_mapcount: 0
flags: 0xfffe0000008100(slab|head)
raw: 00fffe0000008100 ffffea00029cfe08 ffffea000155d408 ffff88821bc44b00
raw: 0000000000000000 ffff88809a7788c0 0000000100000001 0000000000000000
page dumped because: kasan: bad access detected
Memory state around the buggy address:
ffff88809a778b00: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
Memory state around the buggy address:
ffff88809a778b80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
>ffff88809a778c00: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
^
ffff88809a778c80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
ffff88809a778d00: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
syzbot
Sep 27, 2020, 8:05:22 AM9/27/20
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: 10ad6cfd Linux 4.19.148
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11134f03900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11ec280f900000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+3d4253...@syzkaller.appspotmail.com
audit: type=1400 audit(1601205882.263:8): avc: denied { execmem } for pid=6502 comm="syz-executor545" scontext=system_u:system_r:kernel_t:s0 tcontext=system_u:system_r:kernel_t:s0 tclass=process permissive=1
IPVS: ftp: loaded support on port[0] = 21
ntfs: (device loop0): is_boot_sector_ntfs(): Invalid end of sector marker.
CPU: 0 PID: 6503 Comm: syz-executor545 Not tainted 4.19.148-syzkaller #0
Code: b8 08 00 00 00 0f 05 48 3d 01 f0 ff ff 0f 83 1d aa fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 0f 83 fa a9 fb ff c3 66 0f 1f 84 00 00 00 00 00
RSP: 002b:00007ffecff85cc8 EFLAGS: 00000287 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007ffecff85d20 RCX: 000000000044a11a
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007ffecff85ce0
RBP: 0000000000000004 R08: 00007ffecff85d20 R09: 00007ffecff85d10
R10: 0000000000000000 R11: 0000000000000287 R12: 0000000000000003
R13: 00007ffecff85ce0 R14: 0000000000000000 R15: 0000000020001fb0
Allocated by task 6482:
kmem_cache_alloc+0x126/0x4a0 mm/slab.c:3559
kmem_cache_zalloc include/linux/slab.h:699 [inline]
__alloc_file+0x21/0x330 fs/file_table.c:100
alloc_empty_file+0x6d/0x170 fs/file_table.c:150
path_openat+0x12b/0x2e90 fs/namei.c:3526
do_filp_open+0x18c/0x3f0 fs/namei.c:3567
do_sys_open+0x3b3/0x520 fs/open.c:1085
do_syscall_64+0xf9/0x670 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
Freed by task 0:
rcu_do_batch kernel/rcu/tree.c:2584 [inline]
invoke_rcu_callbacks kernel/rcu/tree.c:2897 [inline]
__rcu_process_callbacks kernel/rcu/tree.c:2864 [inline]
rcu_process_callbacks+0x948/0x1d00 kernel/rcu/tree.c:2881
__do_softirq+0x27d/0xad2 kernel/softirq.c:292
The buggy address belongs to the object at ffff8880a3e96000
which belongs to the cache filp of size 456
The buggy address is located 127 bytes inside of
456-byte region [ffff8880a3e96000, ffff8880a3e961c8)
flags: 0xfffe0000000100(slab)
raw: 00fffe0000000100 ffffea00028df348 ffffea00028c96c8 ffff88812c291840
raw: 0000000000000000 ffff8880a3e96000 0000000100000006 0000000000000000
ffff8880a3e95f80: fb fb fb fb fc fc fc fc fc fc fc fc fc fc fc fc
>ffff8880a3e96000: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
^
ffff8880a3e96080: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
ffff8880a3e96100: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
==================================================================
HEAD commit: 10ad6cfd Linux 4.19.148
git tree: linux-4.19.y
kernel config: https://syzkaller.appspot.com/x/.config?x=ef9a7978d84ee42b
dashboard link: https://syzkaller.appspot.com/bug?extid=3d4253be2382d1e54450
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1021d187900000
dashboard link: https://syzkaller.appspot.com/bug?extid=3d4253be2382d1e54450
compiler: gcc (GCC) 10.1.0-syz 20200507
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11ec280f900000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+3d4253...@syzkaller.appspotmail.com
IPVS: ftp: loaded support on port[0] = 21
ntfs: (device loop0): is_boot_sector_ntfs(): Invalid end of sector marker.
==================================================================
BUG: KASAN: use-after-free in ntfs_attr_find+0xa42/0xb70 fs/ntfs/attrib.c:613
Read of size 4 at addr ffff8880a3e9607f by task syz-executor545/6503
BUG: KASAN: use-after-free in ntfs_attr_find+0xa42/0xb70 fs/ntfs/attrib.c:613
CPU: 0 PID: 6503 Comm: syz-executor545 Not tainted 4.19.148-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+0x22c/0x33e lib/dump_stack.c:118
print_address_description.cold+0x56/0x25c mm/kasan/report.c:256
kasan_report_error.cold+0x66/0xb9 mm/kasan/report.c:354
kasan_report mm/kasan/report.c:412 [inline]
__asan_report_load_n_noabort+0x8b/0xa0 mm/kasan/report.c:443
ntfs_attr_find+0xa42/0xb70 fs/ntfs/attrib.c:613
ntfs_attr_lookup+0x1087/0x2060 fs/ntfs/attrib.c:1203
ntfs_read_inode_mount+0x7e4/0x23b0 fs/ntfs/inode.c:1858
ntfs_fill_super+0x1761/0x89d2 fs/ntfs/super.c:2871
mount_bdev+0x2fc/0x3b0 fs/super.c:1158
mount_fs+0xa3/0x318 fs/super.c:1261
vfs_kern_mount.part.0+0x68/0x470 fs/namespace.c:961
vfs_kern_mount fs/namespace.c:951 [inline]
do_new_mount fs/namespace.c:2469 [inline]
do_mount+0x51c/0x2f10 fs/namespace.c:2799
ksys_mount+0xcf/0x130 fs/namespace.c:3015
__do_sys_mount fs/namespace.c:3029 [inline]
__se_sys_mount fs/namespace.c:3026 [inline]
__x64_sys_mount+0xba/0x150 fs/namespace.c:3026
do_syscall_64+0xf9/0x670 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x44a11a
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x22c/0x33e lib/dump_stack.c:118
print_address_description.cold+0x56/0x25c mm/kasan/report.c:256
kasan_report_error.cold+0x66/0xb9 mm/kasan/report.c:354
kasan_report mm/kasan/report.c:412 [inline]
__asan_report_load_n_noabort+0x8b/0xa0 mm/kasan/report.c:443
ntfs_attr_find+0xa42/0xb70 fs/ntfs/attrib.c:613
ntfs_attr_lookup+0x1087/0x2060 fs/ntfs/attrib.c:1203
ntfs_read_inode_mount+0x7e4/0x23b0 fs/ntfs/inode.c:1858
ntfs_fill_super+0x1761/0x89d2 fs/ntfs/super.c:2871
mount_bdev+0x2fc/0x3b0 fs/super.c:1158
mount_fs+0xa3/0x318 fs/super.c:1261
vfs_kern_mount.part.0+0x68/0x470 fs/namespace.c:961
vfs_kern_mount fs/namespace.c:951 [inline]
do_new_mount fs/namespace.c:2469 [inline]
do_mount+0x51c/0x2f10 fs/namespace.c:2799
ksys_mount+0xcf/0x130 fs/namespace.c:3015
__do_sys_mount fs/namespace.c:3029 [inline]
__se_sys_mount fs/namespace.c:3026 [inline]
__x64_sys_mount+0xba/0x150 fs/namespace.c:3026
do_syscall_64+0xf9/0x670 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
Code: b8 08 00 00 00 0f 05 48 3d 01 f0 ff ff 0f 83 1d aa fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 0f 83 fa a9 fb ff c3 66 0f 1f 84 00 00 00 00 00
RSP: 002b:00007ffecff85cc8 EFLAGS: 00000287 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007ffecff85d20 RCX: 000000000044a11a
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007ffecff85ce0
RBP: 0000000000000004 R08: 00007ffecff85d20 R09: 00007ffecff85d10
R10: 0000000000000000 R11: 0000000000000287 R12: 0000000000000003
R13: 00007ffecff85ce0 R14: 0000000000000000 R15: 0000000020001fb0
Allocated by task 6482:
kmem_cache_alloc+0x126/0x4a0 mm/slab.c:3559
kmem_cache_zalloc include/linux/slab.h:699 [inline]
__alloc_file+0x21/0x330 fs/file_table.c:100
alloc_empty_file+0x6d/0x170 fs/file_table.c:150
path_openat+0x12b/0x2e90 fs/namei.c:3526
do_filp_open+0x18c/0x3f0 fs/namei.c:3567
do_sys_open+0x3b3/0x520 fs/open.c:1085
do_syscall_64+0xf9/0x670 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
Freed by task 0:
__cache_free mm/slab.c:3503 [inline]
kmem_cache_free+0x7f/0x2b0 mm/slab.c:3765
__rcu_reclaim kernel/rcu/rcu.h:236 [inline]
kmem_cache_free+0x7f/0x2b0 mm/slab.c:3765
rcu_do_batch kernel/rcu/tree.c:2584 [inline]
invoke_rcu_callbacks kernel/rcu/tree.c:2897 [inline]
__rcu_process_callbacks kernel/rcu/tree.c:2864 [inline]
rcu_process_callbacks+0x948/0x1d00 kernel/rcu/tree.c:2881
__do_softirq+0x27d/0xad2 kernel/softirq.c:292
The buggy address belongs to the object at ffff8880a3e96000
which belongs to the cache filp of size 456
The buggy address is located 127 bytes inside of
456-byte region [ffff8880a3e96000, ffff8880a3e961c8)
The buggy address belongs to the page:
page:ffffea00028fa580 count:1 mapcount:0 mapping:ffff88812c291840 index:0x0
flags: 0xfffe0000000100(slab)
raw: 00fffe0000000100 ffffea00028df348 ffffea00028c96c8 ffff88812c291840
raw: 0000000000000000 ffff8880a3e96000 0000000100000006 0000000000000000
page dumped because: kasan: bad access detected
Memory state around the buggy address:
ffff8880a3e95f00: fb fb fb fb fc fc fc fc fb fb fb fb fc fc fc fc
Memory state around the buggy address:
ffff8880a3e95f80: fb fb fb fb fc fc fc fc fc fc fc fc fc fc fc fc
>ffff8880a3e96000: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
^
ffff8880a3e96080: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
ffff8880a3e96100: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
==================================================================
syzbot
Oct 1, 2020, 3:36:18 AM10/1/20
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: cbfa1702 Linux 4.14.198
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15a79c7b900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1660f1f3900000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+31f564...@syzkaller.appspotmail.com
audit: type=1400 audit(1601537642.898:8): avc: denied { execmem } for pid=6352 comm="syz-executor242" scontext=system_u:system_r:kernel_t:s0 tcontext=system_u:system_r:kernel_t:s0 tclass=process permissive=1
CPU: 1 PID: 6352 Comm: syz-executor242 Not tainted 4.14.198-syzkaller #0
RSP: 002b:00007ffc0a8bb868 EFLAGS: 00000287 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007ffc0a8bb8c0 RCX: 000000000044753a
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007ffc0a8bb880
RBP: 00007ffc0a8bb880 R08: 00007ffc0a8bb8c0 R09: 00007ffc00000015
R10: 0000000000000000 R11: 0000000000000287 R12: 000000000000003a
R13: 0000000000000004 R14: 0000000000000003 R15: 0000000000000003
The buggy address belongs to the page:
page:ffffea00025d3cc0 count:0 mapcount:0 mapping: (null) index:0x0
flags: 0xfffe0000000000()
raw: 00fffe0000000000 0000000000000000 0000000000000000 00000000ffffffff
raw: 0000000000000000 0000000100000001 0000000000000000 0000000000000000
ffff8880974f3c80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>ffff8880974f3d00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
^
ffff8880974f3d80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ffff8880974f3e00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================
HEAD commit: cbfa1702 Linux 4.14.198
git tree: linux-4.14.y
kernel config: https://syzkaller.appspot.com/x/.config?x=3990958d85b55e59
dashboard link: https://syzkaller.appspot.com/bug?extid=31f564ac63c1fb454df9
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1698c683900000
dashboard link: https://syzkaller.appspot.com/bug?extid=31f564ac63c1fb454df9
compiler: gcc (GCC) 10.1.0-syz 20200507
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1660f1f3900000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+31f564...@syzkaller.appspotmail.com
ntfs: (device loop0): is_boot_sector_ntfs(): Invalid end of sector marker.
==================================================================
BUG: KASAN: use-after-free in ntfs_attr_find+0x8df/0xa10 fs/ntfs/attrib.c:613
Read of size 4 at addr ffff8880974f3d00 by task syz-executor242/6352
BUG: KASAN: use-after-free in ntfs_attr_find+0x8df/0xa10 fs/ntfs/attrib.c:613
CPU: 1 PID: 6352 Comm: syz-executor242 Not tainted 4.14.198-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x283 lib/dump_stack.c:58
print_address_description.cold+0x54/0x1d3 mm/kasan/report.c:252
kasan_report_error.cold+0x8a/0x194 mm/kasan/report.c:351
kasan_report mm/kasan/report.c:409 [inline]
__asan_report_load_n_noabort+0x6b/0x80 mm/kasan/report.c:440
ntfs_attr_find+0x8df/0xa10 fs/ntfs/attrib.c:613
ntfs_attr_lookup+0xeca/0x1f30 fs/ntfs/attrib.c:1203
ntfs_read_inode_mount+0x6b4/0x1fb0 fs/ntfs/inode.c:1867
ntfs_fill_super+0x9a6/0x7170 fs/ntfs/super.c:2871
mount_bdev+0x2b3/0x360 fs/super.c:1134
mount_fs+0x92/0x2a0 fs/super.c:1237
vfs_kern_mount.part.0+0x5b/0x470 fs/namespace.c:1046
vfs_kern_mount fs/namespace.c:1036 [inline]
do_new_mount fs/namespace.c:2549 [inline]
do_mount+0xe53/0x2a00 fs/namespace.c:2879
SYSC_mount fs/namespace.c:3095 [inline]
SyS_mount+0xa8/0x120 fs/namespace.c:3072
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x44753a
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x283 lib/dump_stack.c:58
print_address_description.cold+0x54/0x1d3 mm/kasan/report.c:252
kasan_report_error.cold+0x8a/0x194 mm/kasan/report.c:351
kasan_report mm/kasan/report.c:409 [inline]
__asan_report_load_n_noabort+0x6b/0x80 mm/kasan/report.c:440
ntfs_attr_find+0x8df/0xa10 fs/ntfs/attrib.c:613
ntfs_attr_lookup+0xeca/0x1f30 fs/ntfs/attrib.c:1203
ntfs_read_inode_mount+0x6b4/0x1fb0 fs/ntfs/inode.c:1867
ntfs_fill_super+0x9a6/0x7170 fs/ntfs/super.c:2871
mount_bdev+0x2b3/0x360 fs/super.c:1134
mount_fs+0x92/0x2a0 fs/super.c:1237
vfs_kern_mount.part.0+0x5b/0x470 fs/namespace.c:1046
vfs_kern_mount fs/namespace.c:1036 [inline]
do_new_mount fs/namespace.c:2549 [inline]
do_mount+0xe53/0x2a00 fs/namespace.c:2879
SYSC_mount fs/namespace.c:3095 [inline]
SyS_mount+0xa8/0x120 fs/namespace.c:3072
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RSP: 002b:00007ffc0a8bb868 EFLAGS: 00000287 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007ffc0a8bb8c0 RCX: 000000000044753a
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007ffc0a8bb880
RBP: 00007ffc0a8bb880 R08: 00007ffc0a8bb8c0 R09: 00007ffc00000015
R10: 0000000000000000 R11: 0000000000000287 R12: 000000000000003a
R13: 0000000000000004 R14: 0000000000000003 R15: 0000000000000003
The buggy address belongs to the page:
flags: 0xfffe0000000000()
raw: 00fffe0000000000 0000000000000000 0000000000000000 00000000ffffffff
raw: 0000000000000000 0000000100000001 0000000000000000 0000000000000000
page dumped because: kasan: bad access detected
Memory state around the buggy address:
ffff8880974f3c00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Memory state around the buggy address:
ffff8880974f3c80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>ffff8880974f3d00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
^
ffff8880974f3d80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ffff8880974f3e00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================
syzbot
Nov 11, 2020, 2:11:13 PM11/11/20
to syzkaller...@googlegroups.com
syzbot suspects this issue was fixed by commit:
commit d2918cca649f7457018f2c94176a8302e7a9f311
Author: Rustam Kovhaev <rkov...@gmail.com>
Date: Tue Oct 13 23:48:17 2020 +0000
ntfs: add check for mft record size in superblock
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11310f62500000
start commit: cbfa1702 Linux 4.14.198
git tree: linux-4.14.y
#syz fix: ntfs: add check for mft record size in superblock
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
commit d2918cca649f7457018f2c94176a8302e7a9f311
Author: Rustam Kovhaev <rkov...@gmail.com>
Date: Tue Oct 13 23:48:17 2020 +0000
ntfs: add check for mft record size in superblock
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11310f62500000
start commit: cbfa1702 Linux 4.14.198
git tree: linux-4.14.y
kernel config: https://syzkaller.appspot.com/x/.config?x=3990958d85b55e59
dashboard link: https://syzkaller.appspot.com/bug?extid=31f564ac63c1fb454df9
dashboard link: https://syzkaller.appspot.com/bug?extid=31f564ac63c1fb454df9
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1698c683900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1660f1f3900000
If the result looks correct, please mark the issue as fixed by replying with:
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1660f1f3900000
#syz fix: ntfs: add check for mft record size in superblock
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
syzbot
Nov 26, 2020, 11:08:10 PM11/26/20
to syzkaller...@googlegroups.com
syzbot suspects this issue was fixed by commit:
commit dff5d774119537355b01e5b503d9468228d65044
Author: Rustam Kovhaev <rkov...@gmail.com>
Date: Tue Oct 13 23:48:17 2020 +0000
ntfs: add check for mft record size in superblock
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1266d669500000
Date: Tue Oct 13 23:48:17 2020 +0000
ntfs: add check for mft record size in superblock
start commit: ad326970 Linux 4.19.152
git tree: linux-4.19.y
kernel config: https://syzkaller.appspot.com/x/.config?x=1ec7667b405157e
dashboard link: https://syzkaller.appspot.com/bug?extid=3d4253be2382d1e54450
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10ddf5b4500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1367533c500000
Reply all
Reply to author
Forward
0 new messages