[v5.15] KASAN: slab-out-of-bounds Read in ntfs_listxattr

0 views
Skip to first unread message

syzbot

unread,
Mar 28, 2023, 12:37:44 AM3/28/23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 115472395b0a Linux 5.15.104
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14641d05c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=e597b110d58e7b4
dashboard link: https://syzkaller.appspot.com/bug?extid=e1e9bd0f76e9ea4172c0
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/76798ca1c9b6/disk-11547239.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3b608633c8f5/vmlinux-11547239.xz
kernel image: https://storage.googleapis.com/syzbot-assets/8836fafb618b/Image-11547239.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+e1e9bd...@syzkaller.appspotmail.com

ntfs3: loop0: Different NTFS' sector size (4096) and media sector size (512)
ntfs3: loop0: Mark volume as dirty due to NTFS errors
==================================================================
BUG: KASAN: slab-out-of-bounds in ntfs_list_ea fs/ntfs3/xattr.c:187 [inline]
BUG: KASAN: slab-out-of-bounds in ntfs_listxattr+0x290/0x434 fs/ntfs3/xattr.c:708
Read of size 48 at addr ffff00011c165c30 by task syz-executor.0/7151

CPU: 1 PID: 7151 Comm: syz-executor.0 Not tainted 5.15.104-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
Call trace:
dump_backtrace+0x0/0x530 arch/arm64/kernel/stacktrace.c:152
show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:216
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106
print_address_description+0x7c/0x3f0 mm/kasan/report.c:248
__kasan_report mm/kasan/report.c:434 [inline]
kasan_report+0x174/0x1e4 mm/kasan/report.c:451
kasan_check_range+0x274/0x2b4 mm/kasan/generic.c:189
memcpy+0x90/0xe8 mm/kasan/shadow.c:65
ntfs_list_ea fs/ntfs3/xattr.c:187 [inline]
ntfs_listxattr+0x290/0x434 fs/ntfs3/xattr.c:708
vfs_listxattr fs/xattr.c:448 [inline]
listxattr+0x29c/0x3e4 fs/xattr.c:783
path_listxattr fs/xattr.c:807 [inline]
__do_sys_listxattr fs/xattr.c:819 [inline]
__se_sys_listxattr fs/xattr.c:816 [inline]
__arm64_sys_listxattr+0x13c/0x21c fs/xattr.c:816
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584

Allocated by task 7151:
kasan_save_stack mm/kasan/common.c:38 [inline]
kasan_set_track mm/kasan/common.c:46 [inline]
set_alloc_info mm/kasan/common.c:434 [inline]
____kasan_kmalloc+0xbc/0xfc mm/kasan/common.c:513
__kasan_kmalloc+0x10/0x1c mm/kasan/common.c:522
kasan_kmalloc include/linux/kasan.h:264 [inline]
__kmalloc+0x29c/0x4c8 mm/slub.c:4407
kmalloc include/linux/slab.h:596 [inline]
ntfs_read_ea+0x39c/0x6d8 fs/ntfs3/xattr.c:110
ntfs_list_ea fs/ntfs3/xattr.c:168 [inline]
ntfs_listxattr+0x148/0x434 fs/ntfs3/xattr.c:708
vfs_listxattr fs/xattr.c:448 [inline]
listxattr+0x29c/0x3e4 fs/xattr.c:783
path_listxattr fs/xattr.c:807 [inline]
__do_sys_listxattr fs/xattr.c:819 [inline]
__se_sys_listxattr fs/xattr.c:816 [inline]
__arm64_sys_listxattr+0x13c/0x21c fs/xattr.c:816
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584

The buggy address belongs to the object at ffff00011c165c00
which belongs to the cache kmalloc-128 of size 128
The buggy address is located 48 bytes inside of
128-byte region [ffff00011c165c00, ffff00011c165c80)
The buggy address belongs to the page:
page:000000003553b3ac refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x15c165
flags: 0x5ffc00000000200(slab|node=0|zone=2|lastcpupid=0x7ff)
raw: 05ffc00000000200 fffffc000334cc00 0000000700000002 ffff0000c0002300
raw: 0000000000000000 0000000080100010 00000001ffffffff 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
ffff00011c165b00: fa fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
ffff00011c165b80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
>ffff00011c165c00: 00 00 00 00 00 00 00 04 fc fc fc fc fc fc fc fc
^
ffff00011c165c80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
ffff00011c165d00: fa 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

unread,
Mar 28, 2023, 12:14:07 PM3/28/23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: e3a87a10f259 Linux 6.1.21
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1271380dc80000
kernel config: https://syzkaller.appspot.com/x/.config?x=390800ef8aeebc47
dashboard link: https://syzkaller.appspot.com/bug?extid=224664e3588ec766c818
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/9f5022ccd560/disk-e3a87a10.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f8524664c631/vmlinux-e3a87a10.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ad699b30c2c4/Image-e3a87a10.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+224664...@syzkaller.appspotmail.com

ntfs3: loop3: Mark volume as dirty due to NTFS errors
==================================================================
BUG: KASAN: slab-out-of-bounds in ntfs_list_ea fs/ntfs3/xattr.c:187 [inline]
BUG: KASAN: slab-out-of-bounds in ntfs_listxattr+0x290/0x434 fs/ntfs3/xattr.c:710
Read of size 48 at addr ffff0000c91fe330 by task syz-executor.3/12399

CPU: 1 PID: 12399 Comm: syz-executor.3 Not tainted 6.1.21-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
Call trace:
dump_backtrace+0x1c8/0x1f4 arch/arm64/kernel/stacktrace.c:158
show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106
print_address_description mm/kasan/report.c:284 [inline]
print_report+0x174/0x4c0 mm/kasan/report.c:395
kasan_report+0xd4/0x130 mm/kasan/report.c:495
kasan_check_range+0x264/0x2a4 mm/kasan/generic.c:189
memcpy+0x48/0x90 mm/kasan/shadow.c:65
ntfs_list_ea fs/ntfs3/xattr.c:187 [inline]
ntfs_listxattr+0x290/0x434 fs/ntfs3/xattr.c:710
vfs_listxattr fs/xattr.c:457 [inline]
listxattr+0x29c/0x3cc fs/xattr.c:804
path_listxattr fs/xattr.c:828 [inline]
__do_sys_listxattr fs/xattr.c:840 [inline]
__se_sys_listxattr fs/xattr.c:837 [inline]
__arm64_sys_listxattr+0x13c/0x21c fs/xattr.c:837
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:581

Allocated by task 12399:
kasan_save_stack mm/kasan/common.c:45 [inline]
kasan_set_track+0x4c/0x80 mm/kasan/common.c:52
kasan_save_alloc_info+0x24/0x30 mm/kasan/generic.c:505
____kasan_kmalloc mm/kasan/common.c:374 [inline]
__kasan_kmalloc+0xac/0xc4 mm/kasan/common.c:383
kasan_kmalloc include/linux/kasan.h:211 [inline]
__do_kmalloc_node mm/slab_common.c:955 [inline]
__kmalloc+0xd8/0x1c4 mm/slab_common.c:968
kmalloc include/linux/slab.h:558 [inline]
ntfs_read_ea+0x39c/0x6d8 fs/ntfs3/xattr.c:110
ntfs_list_ea fs/ntfs3/xattr.c:168 [inline]
ntfs_listxattr+0x148/0x434 fs/ntfs3/xattr.c:710
vfs_listxattr fs/xattr.c:457 [inline]
listxattr+0x29c/0x3cc fs/xattr.c:804
path_listxattr fs/xattr.c:828 [inline]
__do_sys_listxattr fs/xattr.c:840 [inline]
__se_sys_listxattr fs/xattr.c:837 [inline]
__arm64_sys_listxattr+0x13c/0x21c fs/xattr.c:837
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:581

Last potentially related work creation:
kasan_save_stack+0x40/0x70 mm/kasan/common.c:45
__kasan_record_aux_stack+0xcc/0xe8 mm/kasan/generic.c:486
kasan_record_aux_stack_noalloc+0x14/0x20 mm/kasan/generic.c:496
kvfree_call_rcu+0xb4/0x714 kernel/rcu/tree.c:3343
cfg80211_update_known_bss+0x13c/0x7e0
cfg80211_bss_update+0x160/0x1c64 net/wireless/scan.c:1730
cfg80211_inform_single_bss_frame_data net/wireless/scan.c:2499 [inline]
cfg80211_inform_bss_frame_data+0x99c/0x1d50 net/wireless/scan.c:2532
ieee80211_bss_info_update+0x6a4/0xc78 net/mac80211/scan.c:190
ieee80211_rx_bss_info net/mac80211/ibss.c:1120 [inline]
ieee80211_rx_mgmt_probe_beacon net/mac80211/ibss.c:1609 [inline]
ieee80211_ibss_rx_queued_mgmt+0x954/0x279c net/mac80211/ibss.c:1638
ieee80211_iface_process_skb net/mac80211/iface.c:1632 [inline]
ieee80211_iface_work+0x5c4/0xa90 net/mac80211/iface.c:1686
process_one_work+0x7ac/0x1404 kernel/workqueue.c:2289
worker_thread+0x8e4/0xfec kernel/workqueue.c:2436
kthread+0x24c/0x2d4 kernel/kthread.c:376
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:860

The buggy address belongs to the object at ffff0000c91fe300
which belongs to the cache kmalloc-128 of size 128
The buggy address is located 48 bytes inside of
128-byte region [ffff0000c91fe300, ffff0000c91fe380)

The buggy address belongs to the physical page:
page:000000004a5acb92 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x1091fe
flags: 0x5ffc00000000200(slab|node=0|zone=2|lastcpupid=0x7ff)
raw: 05ffc00000000200 fffffc00032f3240 dead000000000003 ffff0000c0002300
raw: 0000000000000000 0000000080100010 00000001ffffffff 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
ffff0000c91fe200: 05 fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
ffff0000c91fe280: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
>ffff0000c91fe300: 00 00 00 00 00 00 00 04 fc fc fc fc fc fc fc fc
^
ffff0000c91fe380: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
ffff0000c91fe400: 00 fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc

syzbot

unread,
May 5, 2023, 11:29:47 AM5/5/23
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:

HEAD commit: 8a7f2a5c5aa1 Linux 5.15.110
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17e38390280000
kernel config: https://syzkaller.appspot.com/x/.config?x=7e93d602da27af41
dashboard link: https://syzkaller.appspot.com/bug?extid=e1e9bd0f76e9ea4172c0
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17547914280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=127780bc280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/16bea75b636d/disk-8a7f2a5c.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3b169e33dcf2/vmlinux-8a7f2a5c.xz
kernel image: https://storage.googleapis.com/syzbot-assets/190d08a00950/Image-8a7f2a5c.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/0985d117b0db/mount_0.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+e1e9bd...@syzkaller.appspotmail.com

ntfs3: loop0: Different NTFS' sector size (4096) and media sector size (512)
ntfs3: loop0: Mark volume as dirty due to NTFS errors
==================================================================
BUG: KASAN: slab-out-of-bounds in ntfs_list_ea fs/ntfs3/xattr.c:187 [inline]
BUG: KASAN: slab-out-of-bounds in ntfs_listxattr+0x290/0x434 fs/ntfs3/xattr.c:708
Read of size 48 at addr ffff0000cecddb30 by task syz-executor423/3961

CPU: 0 PID: 3961 Comm: syz-executor423 Not tainted 5.15.110-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/2023
Allocated by task 3961:
kasan_save_stack mm/kasan/common.c:38 [inline]
kasan_set_track mm/kasan/common.c:46 [inline]
set_alloc_info mm/kasan/common.c:434 [inline]
____kasan_kmalloc+0xbc/0xfc mm/kasan/common.c:513
__kasan_kmalloc+0x10/0x1c mm/kasan/common.c:522
kasan_kmalloc include/linux/kasan.h:264 [inline]
__kmalloc+0x29c/0x4c8 mm/slub.c:4407
kmalloc include/linux/slab.h:596 [inline]
ntfs_read_ea+0x39c/0x6d8 fs/ntfs3/xattr.c:110
ntfs_list_ea fs/ntfs3/xattr.c:168 [inline]
ntfs_listxattr+0x148/0x434 fs/ntfs3/xattr.c:708
vfs_listxattr fs/xattr.c:448 [inline]
listxattr+0x29c/0x3e4 fs/xattr.c:783
path_listxattr fs/xattr.c:807 [inline]
__do_sys_listxattr fs/xattr.c:819 [inline]
__se_sys_listxattr fs/xattr.c:816 [inline]
__arm64_sys_listxattr+0x13c/0x21c fs/xattr.c:816
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584

The buggy address belongs to the object at ffff0000cecddb00
which belongs to the cache kmalloc-128 of size 128
The buggy address is located 48 bytes inside of
128-byte region [ffff0000cecddb00, ffff0000cecddb80)
The buggy address belongs to the page:
page:0000000062491911 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x10ecdd
flags: 0x5ffc00000000200(slab|node=0|zone=2|lastcpupid=0x7ff)
raw: 05ffc00000000200 dead000000000100 dead000000000122 ffff0000c0002300
raw: 0000000000000000 0000000080100010 00000001ffffffff 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
ffff0000cecdda00: 00 00 00 00 00 00 00 00 00 07 fc fc fc fc fc fc
ffff0000cecdda80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
>ffff0000cecddb00: 00 00 00 00 00 00 00 04 fc fc fc fc fc fc fc fc
^
ffff0000cecddb80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
ffff0000cecddc00: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
==================================================================


---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

syzbot

unread,
Jun 18, 2023, 6:21:50 AM6/18/23
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:

HEAD commit: ca87e77a2ef8 Linux 6.1.34
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13647303280000
kernel config: https://syzkaller.appspot.com/x/.config?x=143044f84cdceac2
dashboard link: https://syzkaller.appspot.com/bug?extid=224664e3588ec766c818
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11524bf7280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=145d10f3280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/1141c37ce351/disk-ca87e77a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/de1fca0d0bb4/vmlinux-ca87e77a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c3417b70e0bf/Image-ca87e77a.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/48aa2619d475/mount_0.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+224664...@syzkaller.appspotmail.com

ntfs3: loop0: Different NTFS' sector size (4096) and media sector size (512)
ntfs3: loop0: Mark volume as dirty due to NTFS errors
==================================================================
BUG: KASAN: slab-out-of-bounds in ntfs_list_ea fs/ntfs3/xattr.c:187 [inline]
BUG: KASAN: slab-out-of-bounds in ntfs_listxattr+0x290/0x434 fs/ntfs3/xattr.c:710
Read of size 48 at addr ffff0000db68be30 by task syz-executor144/4217

CPU: 1 PID: 4217 Comm: syz-executor144 Not tainted 6.1.34-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023
Allocated by task 4217:
The buggy address belongs to the object at ffff0000db68be00
which belongs to the cache kmalloc-128 of size 128
The buggy address is located 48 bytes inside of
128-byte region [ffff0000db68be00, ffff0000db68be80)

The buggy address belongs to the physical page:
page:0000000064170fd7 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x11b68b
flags: 0x5ffc00000000200(slab|node=0|zone=2|lastcpupid=0x7ff)
raw: 05ffc00000000200 0000000000000000 dead000000000001 ffff0000c0002300
raw: 0000000000000000 0000000080100010 00000001ffffffff 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
ffff0000db68bd00: fa fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
ffff0000db68bd80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
>ffff0000db68be00: 00 00 00 00 00 00 00 04 fc fc fc fc fc fc fc fc
^
ffff0000db68be80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
ffff0000db68bf00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

syzbot

unread,
Mar 30, 2024, 3:59:06 PMMar 30
to syzkaller...@googlegroups.com
syzbot suspects this issue was fixed by commit:

commit 6ed6cdbe88334ca3430c5aee7754dc4597498dfb
Author: Edward Adam Davis <ead...@qq.com>
Date: Sat Dec 30 09:00:03 2023 +0000

fs/ntfs3: Fix oob in ntfs_listxattr

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1085f2b5180000
start commit: 4aa6747d9352 Linux 6.1.69
git tree: linux-6.1.y
kernel config: https://syzkaller.appspot.com/x/.config?x=e1e9066810307299
dashboard link: https://syzkaller.appspot.com/bug?extid=224664e3588ec766c818
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=138f9595e80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13dec9a1e80000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: fs/ntfs3: Fix oob in ntfs_listxattr

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

syzbot

unread,
7:40 AM (2 hours ago) 7:40 AM
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
No recent activity, existing reproducers are no longer triggering the issue.
Reply all
Reply to author
Forward
0 new messages