* [syzbot] [crypto?] KASAN: use-after-free Read in crypto_poly1305_update
@ 2025-02-17 7:53 syzbot
2025-02-17 10:24 ` Ard Biesheuvel
` (3 more replies)
0 siblings, 4 replies; 5+ messages in thread
From: syzbot @ 2025-02-17 7:53 UTC (permalink / raw)
To: bp, dave.hansen, davem, herbert, hpa, linux-crypto, linux-kernel,
mingo, syzkaller-bugs, tglx, x86
Hello,
syzbot found the following issue on:
HEAD commit: ba643b6d8440 Merge tag 'irq_urgent_for_v6.14_rc3' of git:/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=176ea898580000
kernel config: https://syzkaller.appspot.com/x/.config?x=c776e555cfbdb82d
dashboard link: https://syzkaller.appspot.com/bug?extid=d587b24799bd8c2d32f4
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=150557df980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10eea898580000
Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7feb34a89c2a/non_bootable_disk-ba643b6d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b6a86fb77c0b/vmlinux-ba643b6d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c4725da84fe0/bzImage-ba643b6d.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/769f8967e4f1/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+d587b24799bd8c2d32f4@syzkaller.appspotmail.com
==================================================================
BUG: KASAN: use-after-free in crypto_poly1305_update+0x28/0x40 arch/x86/crypto/poly1305_glue.c:230
Read of size 8 at addr ffff888049757390 by task syz-executor358/5305
CPU: 0 UID: 0 PID: 5305 Comm: syz-executor358 Not tainted 6.14.0-rc2-syzkaller-00346-gba643b6d8440 #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:94 [inline]
dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120
print_address_description mm/kasan/report.c:378 [inline]
print_report+0x169/0x550 mm/kasan/report.c:489
kasan_report+0x143/0x180 mm/kasan/report.c:602
kasan_check_range+0x282/0x290 mm/kasan/generic.c:189
__asan_memcpy+0x29/0x70 mm/kasan/shadow.c:105
crypto_poly1305_update+0x28/0x40 arch/x86/crypto/poly1305_glue.c:230
bch2_checksum+0x5fa/0x780 fs/bcachefs/checksum.c:239
bch2_btree_node_read_done+0x1402/0x6180 fs/bcachefs/btree_io.c:1130
btree_node_read_work+0x6dc/0x1380 fs/bcachefs/btree_io.c:1358
bch2_btree_node_read+0x2433/0x29f0
__bch2_btree_root_read fs/bcachefs/btree_io.c:1789 [inline]
bch2_btree_root_read+0x626/0x7b0 fs/bcachefs/btree_io.c:1811
read_btree_roots+0x3d3/0xa70 fs/bcachefs/recovery.c:581
bch2_fs_recovery+0x260f/0x3de0 fs/bcachefs/recovery.c:928
bch2_fs_start+0x37c/0x610 fs/bcachefs/super.c:1041
bch2_fs_get_tree+0xdb7/0x17a0 fs/bcachefs/fs.c:2203
vfs_get_tree+0x90/0x2b0 fs/super.c:1814
do_new_mount+0x2be/0xb40 fs/namespace.c:3560
do_mount fs/namespace.c:3900 [inline]
__do_sys_mount fs/namespace.c:4111 [inline]
__se_sys_mount+0x2d6/0x3c0 fs/namespace.c:4088
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fd8b49b71ba
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 5e 04 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fff5a4d7e78 EFLAGS: 00000282 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007fff5a4d7e90 RCX: 00007fd8b49b71ba
RDX: 0000400000000000 RSI: 0000400000000200 RDI: 00007fff5a4d7e90
RBP: 0000400000000000 R08: 00007fff5a4d7ed0 R09: 000000000000f634
R10: 0000000002a08414 R11: 0000000000000282 R12: 0000400000000200
R13: 00007fff5a4d7ed0 R14: 0000000000000003 R15: 0000000002a08414
</TASK>
The buggy address belongs to the physical page:
page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x49757
flags: 0x4fff00000000000(node=1|zone=1|lastcpupid=0x7ff)
raw: 04fff00000000000 ffffea000125d5c8 ffffea000125d5c8 0000000000000000
raw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000
page dumped because: kasan: bad access detected
page_owner info is not present (never set?)
Memory state around the buggy address:
ffff888049757280: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ffff888049757300: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>ffff888049757380: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
^
ffff888049757400: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ffff888049757480: 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 syzkaller@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 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.
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [syzbot] [crypto?] KASAN: use-after-free Read in crypto_poly1305_update
2025-02-17 7:53 [syzbot] [crypto?] KASAN: use-after-free Read in crypto_poly1305_update syzbot
@ 2025-02-17 10:24 ` Ard Biesheuvel
2025-02-18 22:05 ` [syzbot] [bcachefs] " syzbot
` (2 subsequent siblings)
3 siblings, 0 replies; 5+ messages in thread
From: Ard Biesheuvel @ 2025-02-17 10:24 UTC (permalink / raw)
To: syzbot
Cc: bp, dave.hansen, davem, herbert, hpa, linux-crypto, linux-kernel,
mingo, syzkaller-bugs, tglx, x86
#syz set subsystems: bcachefs
On Mon, 17 Feb 2025 at 08:53, syzbot
<syzbot+d587b24799bd8c2d32f4@syzkaller.appspotmail.com> wrote:
>
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: ba643b6d8440 Merge tag 'irq_urgent_for_v6.14_rc3' of git:/..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=176ea898580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=c776e555cfbdb82d
> dashboard link: https://syzkaller.appspot.com/bug?extid=d587b24799bd8c2d32f4
> compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=150557df980000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10eea898580000
>
> Downloadable assets:
> disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7feb34a89c2a/non_bootable_disk-ba643b6d.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/b6a86fb77c0b/vmlinux-ba643b6d.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/c4725da84fe0/bzImage-ba643b6d.xz
> mounted in repro: https://storage.googleapis.com/syzbot-assets/769f8967e4f1/mount_0.gz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+d587b24799bd8c2d32f4@syzkaller.appspotmail.com
>
> ==================================================================
> BUG: KASAN: use-after-free in crypto_poly1305_update+0x28/0x40 arch/x86/crypto/poly1305_glue.c:230
> Read of size 8 at addr ffff888049757390 by task syz-executor358/5305
>
> CPU: 0 UID: 0 PID: 5305 Comm: syz-executor358 Not tainted 6.14.0-rc2-syzkaller-00346-gba643b6d8440 #0
> Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
> Call Trace:
> <TASK>
> __dump_stack lib/dump_stack.c:94 [inline]
> dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120
> print_address_description mm/kasan/report.c:378 [inline]
> print_report+0x169/0x550 mm/kasan/report.c:489
> kasan_report+0x143/0x180 mm/kasan/report.c:602
> kasan_check_range+0x282/0x290 mm/kasan/generic.c:189
> __asan_memcpy+0x29/0x70 mm/kasan/shadow.c:105
> crypto_poly1305_update+0x28/0x40 arch/x86/crypto/poly1305_glue.c:230
> bch2_checksum+0x5fa/0x780 fs/bcachefs/checksum.c:239
> bch2_btree_node_read_done+0x1402/0x6180 fs/bcachefs/btree_io.c:1130
> btree_node_read_work+0x6dc/0x1380 fs/bcachefs/btree_io.c:1358
> bch2_btree_node_read+0x2433/0x29f0
> __bch2_btree_root_read fs/bcachefs/btree_io.c:1789 [inline]
> bch2_btree_root_read+0x626/0x7b0 fs/bcachefs/btree_io.c:1811
> read_btree_roots+0x3d3/0xa70 fs/bcachefs/recovery.c:581
> bch2_fs_recovery+0x260f/0x3de0 fs/bcachefs/recovery.c:928
> bch2_fs_start+0x37c/0x610 fs/bcachefs/super.c:1041
> bch2_fs_get_tree+0xdb7/0x17a0 fs/bcachefs/fs.c:2203
> vfs_get_tree+0x90/0x2b0 fs/super.c:1814
> do_new_mount+0x2be/0xb40 fs/namespace.c:3560
> do_mount fs/namespace.c:3900 [inline]
> __do_sys_mount fs/namespace.c:4111 [inline]
> __se_sys_mount+0x2d6/0x3c0 fs/namespace.c:4088
> do_syscall_x64 arch/x86/entry/common.c:52 [inline]
> do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
> entry_SYSCALL_64_after_hwframe+0x77/0x7f
> RIP: 0033:0x7fd8b49b71ba
> Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 5e 04 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
> RSP: 002b:00007fff5a4d7e78 EFLAGS: 00000282 ORIG_RAX: 00000000000000a5
> RAX: ffffffffffffffda RBX: 00007fff5a4d7e90 RCX: 00007fd8b49b71ba
> RDX: 0000400000000000 RSI: 0000400000000200 RDI: 00007fff5a4d7e90
> RBP: 0000400000000000 R08: 00007fff5a4d7ed0 R09: 000000000000f634
> R10: 0000000002a08414 R11: 0000000000000282 R12: 0000400000000200
> R13: 00007fff5a4d7ed0 R14: 0000000000000003 R15: 0000000002a08414
> </TASK>
>
> The buggy address belongs to the physical page:
> page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x49757
> flags: 0x4fff00000000000(node=1|zone=1|lastcpupid=0x7ff)
> raw: 04fff00000000000 ffffea000125d5c8 ffffea000125d5c8 0000000000000000
> raw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000
> page dumped because: kasan: bad access detected
> page_owner info is not present (never set?)
>
> Memory state around the buggy address:
> ffff888049757280: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ffff888049757300: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >ffff888049757380: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ^
> ffff888049757400: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ffff888049757480: 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 syzkaller@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 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.
>
> 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
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [syzbot] [bcachefs] KASAN: use-after-free Read in crypto_poly1305_update
2025-02-17 7:53 [syzbot] [crypto?] KASAN: use-after-free Read in crypto_poly1305_update syzbot
2025-02-17 10:24 ` Ard Biesheuvel
@ 2025-02-18 22:05 ` syzbot
2025-07-17 20:49 ` syzbot
2025-07-17 21:45 ` Forwarded: " syzbot
3 siblings, 0 replies; 5+ messages in thread
From: syzbot @ 2025-02-18 22:05 UTC (permalink / raw)
To: bfoster, bp, dave.hansen, davem, herbert, hpa, kent.overstreet,
linux-bcachefs, linux-crypto, linux-kernel, mingo, syzkaller-bugs,
tglx, x86
syzbot has bisected this issue to:
commit 03ef80b469d5d83530ce1ce15be78a40e5300f9b
Author: Kent Overstreet <kent.overstreet@linux.dev>
Date: Sat Sep 23 22:41:51 2023 +0000
bcachefs: Ignore unknown mount options
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15a303a4580000
start commit: 2408a807bfc3 Merge tag 'vfs-6.14-rc4.fixes' of git://git.k..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=17a303a4580000
console output: https://syzkaller.appspot.com/x/log.txt?x=13a303a4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=6cc40dfe827ffb85
dashboard link: https://syzkaller.appspot.com/bug?extid=d587b24799bd8c2d32f4
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12c4f2e4580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17e4c498580000
Reported-by: syzbot+d587b24799bd8c2d32f4@syzkaller.appspotmail.com
Fixes: 03ef80b469d5 ("bcachefs: Ignore unknown mount options")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [syzbot] [bcachefs] KASAN: use-after-free Read in crypto_poly1305_update
2025-02-17 7:53 [syzbot] [crypto?] KASAN: use-after-free Read in crypto_poly1305_update syzbot
2025-02-17 10:24 ` Ard Biesheuvel
2025-02-18 22:05 ` [syzbot] [bcachefs] " syzbot
@ 2025-07-17 20:49 ` syzbot
2025-07-17 21:45 ` Forwarded: " syzbot
3 siblings, 0 replies; 5+ messages in thread
From: syzbot @ 2025-07-17 20:49 UTC (permalink / raw)
To: bfoster, bp, dave.hansen, davem, herbert, hpa, kent.overstreet,
linux-bcachefs, linux-crypto, linux-kernel, mingo, mmpgouride,
syzkaller-bugs, tglx, x86
syzbot suspects this issue was fixed by commit:
commit d89a34b14df5c205de698c23c3950b2b947cdb97
Author: Alan Huang <mmpgouride@gmail.com>
Date: Sat Jun 14 09:18:07 2025 +0000
bcachefs: Move bset size check before csum check
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1722a58c580000
start commit: 2408a807bfc3 Merge tag 'vfs-6.14-rc4.fixes' of git://git.k..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=6cc40dfe827ffb85
dashboard link: https://syzkaller.appspot.com/bug?extid=d587b24799bd8c2d32f4
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12c4f2e4580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17e4c498580000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: bcachefs: Move bset size check before csum check
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
^ permalink raw reply [flat|nested] 5+ messages in thread
* Forwarded: Re: [syzbot] [bcachefs] KASAN: use-after-free Read in crypto_poly1305_update
2025-02-17 7:53 [syzbot] [crypto?] KASAN: use-after-free Read in crypto_poly1305_update syzbot
` (2 preceding siblings ...)
2025-07-17 20:49 ` syzbot
@ 2025-07-17 21:45 ` syzbot
3 siblings, 0 replies; 5+ messages in thread
From: syzbot @ 2025-07-17 21:45 UTC (permalink / raw)
To: linux-kernel, syzkaller-bugs
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: Re: [syzbot] [bcachefs] KASAN: use-after-free Read in crypto_poly1305_update
Author: kent.overstreet@linux.dev
On Thu, Jul 17, 2025 at 01:49:03PM -0700, syzbot wrote:
> syzbot suspects this issue was fixed by commit:
>
> commit d89a34b14df5c205de698c23c3950b2b947cdb97
> Author: Alan Huang <mmpgouride@gmail.com>
> Date: Sat Jun 14 09:18:07 2025 +0000
>
> bcachefs: Move bset size check before csum check
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1722a58c580000
> start commit: 2408a807bfc3 Merge tag 'vfs-6.14-rc4.fixes' of git://git.k..
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=6cc40dfe827ffb85
> dashboard link: https://syzkaller.appspot.com/bug?extid=d587b24799bd8c2d32f4
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12c4f2e4580000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17e4c498580000
>
> If the result looks correct, please mark the issue as fixed by replying with:
>
#syz fix: bcachefs: Move bset size check before csum check
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2025-07-17 21:45 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-02-17 7:53 [syzbot] [crypto?] KASAN: use-after-free Read in crypto_poly1305_update syzbot
2025-02-17 10:24 ` Ard Biesheuvel
2025-02-18 22:05 ` [syzbot] [bcachefs] " syzbot
2025-07-17 20:49 ` syzbot
2025-07-17 21:45 ` Forwarded: " 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).