[v5.15] KASAN: use-after-free Write in ntfs_perform_write

3 views
Skip to first unread message

syzbot

unread,
Dec 29, 2023, 9:37:21 AM12/29/23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: d93fa2c78854 Linux 5.15.145
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16ad1455e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=8eb25e663e3df1b9
dashboard link: https://syzkaller.appspot.com/bug?extid=5117b878bc7786997c06
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/45f65ff2a6ba/disk-d93fa2c7.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/983a4d12af77/vmlinux-d93fa2c7.xz
kernel image: https://storage.googleapis.com/syzbot-assets/8864285a1d94/Image-d93fa2c7.gz.xz

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

ntfs: volume version 3.1.
==================================================================
BUG: KASAN: use-after-free in ntfs_commit_pages_after_write fs/ntfs/file.c:1608 [inline]
BUG: KASAN: use-after-free in ntfs_perform_write+0x4110/0x66b8 fs/ntfs/file.c:1864
Write of size 1 at addr ffff000110421170 by task syz-executor.4/18036

CPU: 0 PID: 18036 Comm: syz-executor.4 Not tainted 5.15.145-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/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+0xb4/0xe8 mm/kasan/shadow.c:66
ntfs_commit_pages_after_write fs/ntfs/file.c:1608 [inline]
ntfs_perform_write+0x4110/0x66b8 fs/ntfs/file.c:1864
ntfs_file_write_iter+0xfa4/0x170c fs/ntfs/file.c:1921
call_write_iter include/linux/fs.h:2146 [inline]
new_sync_write fs/read_write.c:507 [inline]
vfs_write+0x87c/0xb3c fs/read_write.c:594
ksys_write+0x15c/0x26c fs/read_write.c:647
__do_sys_write fs/read_write.c:659 [inline]
__se_sys_write fs/read_write.c:656 [inline]
__arm64_sys_write+0x7c/0x90 fs/read_write.c:656
__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:608
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584

The buggy address belongs to the page:
page:00000000ed69c44c refcount:0 mapcount:0 mapping:0000000000000000 index:0x1 pfn:0x150421
flags: 0x5ffc00000000000(node=0|zone=2|lastcpupid=0x7ff)
raw: 05ffc00000000000 fffffc0004d01908 fffffc0004413a48 0000000000000000
raw: 0000000000000001 0000000000000000 00000000ffffffff 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
ffff000110421000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ffff000110421080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>ffff000110421100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
^
ffff000110421180: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ffff000110421200: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================


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

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

syzbot

unread,
Jan 1, 2024, 11:19:22 AMJan 1
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: a507f147e6f0 Linux 6.1.70
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1514a7cee80000
kernel config: https://syzkaller.appspot.com/x/.config?x=af33470cb003e14e
dashboard link: https://syzkaller.appspot.com/bug?extid=1e713edef6050354c72f
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7157b698190b/disk-a507f147.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/075d989b469b/vmlinux-a507f147.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f18b4225d20b/Image-a507f147.gz.xz

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

==================================================================
BUG: KASAN: use-after-free in ntfs_commit_pages_after_write fs/ntfs/file.c:1604 [inline]
BUG: KASAN: use-after-free in ntfs_perform_write+0x4288/0x6ef4 fs/ntfs/file.c:1860
Write of size 1 at addr ffff0001010c2170 by task syz-executor.5/12428

CPU: 1 PID: 12428 Comm: syz-executor.5 Not tainted 6.1.70-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/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+0x60/0x90 mm/kasan/shadow.c:66
ntfs_commit_pages_after_write fs/ntfs/file.c:1604 [inline]
ntfs_perform_write+0x4288/0x6ef4 fs/ntfs/file.c:1860
ntfs_file_write_iter+0xf78/0x17b0 fs/ntfs/file.c:1917
call_write_iter include/linux/fs.h:2248 [inline]
new_sync_write fs/read_write.c:491 [inline]
vfs_write+0x610/0x914 fs/read_write.c:584
ksys_write+0x15c/0x26c fs/read_write.c:637
__do_sys_write fs/read_write.c:649 [inline]
__se_sys_write fs/read_write.c:646 [inline]
__arm64_sys_write+0x7c/0x90 fs/read_write.c:646
__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:585

The buggy address belongs to the physical page:
page:000000000a142f92 refcount:0 mapcount:0 mapping:0000000000000000 index:0x1 pfn:0x1410c2
flags: 0x5ffc00000000000(node=0|zone=2|lastcpupid=0x7ff)
raw: 05ffc00000000000 dead000000000100 dead000000000122 0000000000000000
raw: 0000000000000001 0000000000000000 00000000ffffffff 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
ffff0001010c2000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ffff0001010c2080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>ffff0001010c2100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
^
ffff0001010c2180: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ffff0001010c2200: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff

syzbot

unread,
Jan 1, 2024, 8:23:19 PMJan 1
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:

HEAD commit: a507f147e6f0 Linux 6.1.70
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1286b32de80000
kernel config: https://syzkaller.appspot.com/x/.config?x=af33470cb003e14e
dashboard link: https://syzkaller.appspot.com/bug?extid=1e713edef6050354c72f
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11a7ba7ee80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17e9c9a1e80000
mounted in repro: https://storage.googleapis.com/syzbot-assets/683b8a396f2d/mount_0.gz

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

ntfs: (device loop0): parse_options(): Option utf8 is no longer supported, using option nls=utf8. Please use option nls=utf8 in the future and make sure utf8 is compiled either as a module or into the kernel.
ntfs: volume version 3.1.
==================================================================
BUG: KASAN: use-after-free in ntfs_commit_pages_after_write fs/ntfs/file.c:1604 [inline]
BUG: KASAN: use-after-free in ntfs_perform_write+0x4288/0x6ef4 fs/ntfs/file.c:1860
Write of size 1 at addr ffff0000e29d8170 by task syz-executor309/4230

CPU: 1 PID: 4230 Comm: syz-executor309 Not tainted 6.1.70-syzkaller #0
page:00000000689effa6 refcount:0 mapcount:0 mapping:0000000000000000 index:0x1 pfn:0x1229d8
flags: 0x5ffc00000000000(node=0|zone=2|lastcpupid=0x7ff)
raw: 05ffc00000000000 fffffc00038a7648 fffffc00038a75c8 0000000000000000
raw: 0000000000000001 0000000000000000 00000000ffffffff 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
ffff0000e29d8000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ffff0000e29d8080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>ffff0000e29d8100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
^
ffff0000e29d8180: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ffff0000e29d8200: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================


---
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,
Jan 4, 2024, 12:43:20 AMJan 4
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:

HEAD commit: d93fa2c78854 Linux 5.15.145
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1585f31ae80000
kernel config: https://syzkaller.appspot.com/x/.config?x=8eb25e663e3df1b9
dashboard link: https://syzkaller.appspot.com/bug?extid=5117b878bc7786997c06
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17f95b95e80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=105fdd91e80000
mounted in repro: https://storage.googleapis.com/syzbot-assets/81409dab5fed/mount_0.gz

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

ntfs: (device loop0): parse_options(): Option utf8 is no longer supported, using option nls=utf8. Please use option nls=utf8 in the future and make sure utf8 is compiled either as a module or into the kernel.
ntfs: volume version 3.1.
==================================================================
BUG: KASAN: use-after-free in ntfs_commit_pages_after_write fs/ntfs/file.c:1608 [inline]
BUG: KASAN: use-after-free in ntfs_perform_write+0x4110/0x66b8 fs/ntfs/file.c:1864
Write of size 1 at addr ffff0000dd20e170 by task syz-executor159/3968

CPU: 0 PID: 3968 Comm: syz-executor159 Not tainted 5.15.145-syzkaller #0
page:000000008231391d refcount:0 mapcount:0 mapping:0000000000000000 index:0x1 pfn:0x11d20e
flags: 0x5ffc00000000000(node=0|zone=2|lastcpupid=0x7ff)
raw: 05ffc00000000000 fffffc00037483c8 fffffc0003748348 0000000000000000
raw: 0000000000000001 0000000000000000 00000000ffffffff 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
ffff0000dd20e000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ffff0000dd20e080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>ffff0000dd20e100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
^
ffff0000dd20e180: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ffff0000dd20e200: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================


---
Reply all
Reply to author
Forward
0 new messages