syzbot


KASAN: invalid-access Write in do_bad_area

Status: upstream: reported on 2025/10/05 10:08
Subsystems: bpf
[Documentation on labels]
Reported-by: syzbot+997752115a851cb0cf36@syzkaller.appspotmail.com
First crash: 4d13h, last: 3h41m
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [bpf?] KASAN: invalid-access Write in do_bad_area 0 (1) 2025/10/05 10:08

Sample crash report:
==================================================================
BUG: KASAN: invalid-access in __memcpy+0xc/0x54 arch/arm64/lib/memcpy.S:250
Write at addr f1ff8000833e5267 by task syz.1.42/3573
Pointer tag: [f1], memory tag: [fe]

CPU: 1 UID: 0 PID: 3573 Comm: syz.1.42 Not tainted syzkaller #0 PREEMPT 
Hardware name: linux,dummy-virt (DT)
Call trace:
 show_stack+0x18/0x24 arch/arm64/kernel/stacktrace.c:499 (C)
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x78/0x90 lib/dump_stack.c:120
 print_address_description mm/kasan/report.c:378 [inline]
 print_report+0x108/0x61c mm/kasan/report.c:482
 kasan_report+0x88/0xac mm/kasan/report.c:595
 report_tag_fault arch/arm64/mm/fault.c:326 [inline]
 do_tag_recovery arch/arm64/mm/fault.c:338 [inline]
 __do_kernel_fault+0x170/0x1c8 arch/arm64/mm/fault.c:380
 do_bad_area+0x68/0x78 arch/arm64/mm/fault.c:480
 do_tag_check_fault+0x34/0x44 arch/arm64/mm/fault.c:853
 do_mem_abort+0x44/0x94 arch/arm64/mm/fault.c:929
 el1_abort+0x44/0x68 arch/arm64/kernel/entry-common.c:325
 el1h_64_sync_handler+0x50/0xac arch/arm64/kernel/entry-common.c:459
 el1h_64_sync+0x6c/0x70 arch/arm64/kernel/entry.S:591
 __memcpy+0xc/0x54 arch/arm64/lib/memcpy.S:250 (P)
 do_misc_fixups+0x14bc/0x1aac kernel/bpf/verifier.c:22636
 bpf_check+0x1348/0x2a24 kernel/bpf/verifier.c:24686
 bpf_prog_load+0x63c/0xcd4 kernel/bpf/syscall.c:3062
 __sys_bpf+0x2e0/0x1a88 kernel/bpf/syscall.c:6134
 __do_sys_bpf kernel/bpf/syscall.c:6244 [inline]
 __se_sys_bpf kernel/bpf/syscall.c:6242 [inline]
 __arm64_sys_bpf+0x24/0x34 kernel/bpf/syscall.c:6242
 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
 invoke_syscall+0x48/0x110 arch/arm64/kernel/syscall.c:49
 el0_svc_common.constprop.0+0xc0/0xe0 arch/arm64/kernel/syscall.c:132
 do_el0_svc+0x1c/0x28 arch/arm64/kernel/syscall.c:151
 el0_svc+0x34/0x10c arch/arm64/kernel/entry-common.c:744
 el0t_64_sync_handler+0xa0/0xe4 arch/arm64/kernel/entry-common.c:763
 el0t_64_sync+0x1a4/0x1a8 arch/arm64/kernel/entry.S:596

The buggy address belongs to a 1-page vmalloc region starting at 0xf1ff8000833e5000 allocated at bpf_check+0x8c/0x2a24 kernel/bpf/verifier.c:24529
The buggy address belongs to the physical page:
page: refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x4caba
flags: 0x1fff80000000000(node=0|zone=0|lastcpupid=0x7ff|kasantag=0xe)
raw: 01fff80000000000 0000000000000000 dead000000000122 0000000000000000
raw: 0000000000000000 0000000000000000 00000001ffffffff 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
 ffff8000833e5000: f1 f1 f1 f1 f1 f1 f1 f1 f1 f1 f1 f1 f1 f1 f1 f1
 ffff8000833e5100: f1 f1 f1 f1 f1 f1 f1 f1 f1 f1 f1 f1 f1 f1 f1 f1
>ffff8000833e5200: f1 fe fe fe fe fe fe fe fe fe fe fe fe fe fe fe
                                     ^
 ffff8000833e5300: fe fe fe fe fe fe fe fe fe fe fe fe fe fe fe fe
 ffff8000833e5400: fe fe fe fe fe fe fe fe fe fe fe fe fe fe fe fe
==================================================================

Crashes (1549):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/10/05 19:20 upstream 6093a688a07d 49379ee0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-mte KASAN: invalid-access Write in do_bad_area
2025/10/05 19:02 upstream 6093a688a07d 49379ee0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-mte KASAN: invalid-access Write in do_bad_area
2025/10/05 18:38 upstream 6093a688a07d 49379ee0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-mte KASAN: invalid-access Write in do_bad_area
2025/10/05 18:18 upstream 6093a688a07d 49379ee0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-mte KASAN: invalid-access Write in do_bad_area
2025/10/05 17:59 upstream 6093a688a07d 49379ee0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-mte KASAN: invalid-access Write in do_bad_area
2025/10/05 17:42 upstream 6093a688a07d 49379ee0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-mte KASAN: invalid-access Write in do_bad_area
2025/10/05 17:26 upstream 6093a688a07d 49379ee0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-mte KASAN: invalid-access Write in do_bad_area
2025/10/05 17:09 upstream 6093a688a07d 49379ee0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-mte KASAN: invalid-access Write in do_bad_area
2025/10/05 16:45 upstream 6093a688a07d 49379ee0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-mte KASAN: invalid-access Write in do_bad_area
2025/10/05 16:28 upstream 6093a688a07d 49379ee0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-mte KASAN: invalid-access Write in do_bad_area
2025/10/05 16:02 upstream 6093a688a07d 49379ee0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-mte KASAN: invalid-access Write in do_bad_area
2025/10/05 15:57 upstream 6093a688a07d 49379ee0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-mte KASAN: invalid-access Write in do_bad_area
2025/10/05 05:45 upstream cbf33b8e0b36 49379ee0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-mte KASAN: invalid-access Write in do_bad_area
2025/10/05 05:24 upstream cbf33b8e0b36 49379ee0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-mte KASAN: invalid-access Write in do_bad_area
2025/10/05 05:01 upstream cbf33b8e0b36 49379ee0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-mte KASAN: invalid-access Write in do_bad_area
2025/10/05 04:33 upstream cbf33b8e0b36 49379ee0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-mte KASAN: invalid-access Write in do_bad_area
2025/10/05 04:13 upstream cbf33b8e0b36 49379ee0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-mte KASAN: invalid-access Write in do_bad_area
2025/10/05 03:56 upstream cbf33b8e0b36 49379ee0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-mte KASAN: invalid-access Write in do_bad_area
2025/10/05 03:43 upstream cbf33b8e0b36 49379ee0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-mte KASAN: invalid-access Write in do_bad_area
2025/10/05 03:24 upstream cbf33b8e0b36 49379ee0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-mte KASAN: invalid-access Write in do_bad_area
2025/10/05 03:09 upstream cbf33b8e0b36 49379ee0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-mte KASAN: invalid-access Write in do_bad_area
2025/10/05 02:55 upstream cbf33b8e0b36 49379ee0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-mte KASAN: invalid-access Write in do_bad_area
2025/10/05 02:39 upstream cbf33b8e0b36 49379ee0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-mte KASAN: invalid-access Write in do_bad_area
2025/10/05 02:27 upstream cbf33b8e0b36 49379ee0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-mte KASAN: invalid-access Write in do_bad_area
2025/10/05 02:21 upstream cbf33b8e0b36 49379ee0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-mte KASAN: invalid-access Write in do_bad_area
2025/10/04 16:18 upstream 2ccb4d203fe4 49379ee0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-mte KASAN: invalid-access Write in do_bad_area
2025/10/04 16:02 upstream 2ccb4d203fe4 49379ee0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-mte KASAN: invalid-access Write in do_bad_area
2025/10/04 15:46 upstream 2ccb4d203fe4 49379ee0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-mte KASAN: invalid-access Write in do_bad_area
2025/10/04 15:28 upstream 2ccb4d203fe4 49379ee0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-mte KASAN: invalid-access Write in do_bad_area
2025/10/04 15:13 upstream 2ccb4d203fe4 49379ee0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-mte KASAN: invalid-access Write in do_bad_area
2025/10/04 14:53 upstream 2ccb4d203fe4 49379ee0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-mte KASAN: invalid-access Write in do_bad_area
2025/10/04 14:33 upstream 2ccb4d203fe4 49379ee0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-mte KASAN: invalid-access Write in do_bad_area
2025/10/04 14:11 upstream 2ccb4d203fe4 49379ee0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-mte KASAN: invalid-access Write in do_bad_area
2025/10/04 13:57 upstream 2ccb4d203fe4 49379ee0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-mte KASAN: invalid-access Write in do_bad_area
2025/10/04 13:41 upstream 2ccb4d203fe4 49379ee0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-mte KASAN: invalid-access Write in do_bad_area
2025/10/04 13:18 upstream 2ccb4d203fe4 49379ee0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-mte KASAN: invalid-access Write in do_bad_area
2025/10/04 13:10 upstream 2ccb4d203fe4 49379ee0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-mte KASAN: invalid-access Write in do_bad_area
2025/10/04 02:55 upstream e406d57be7bd 49379ee0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-mte KASAN: invalid-access Write in do_bad_area
2025/10/04 02:40 upstream e406d57be7bd 49379ee0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-mte KASAN: invalid-access Write in do_bad_area
2025/10/04 02:24 upstream e406d57be7bd 49379ee0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-mte KASAN: invalid-access Write in do_bad_area
2025/10/04 02:04 upstream e406d57be7bd 49379ee0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-mte KASAN: invalid-access Write in do_bad_area
2025/10/04 01:46 upstream e406d57be7bd 49379ee0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-mte KASAN: invalid-access Write in do_bad_area
2025/10/04 01:28 upstream e406d57be7bd 49379ee0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-mte KASAN: invalid-access Write in do_bad_area
2025/10/01 10:07 upstream 50c19e20ed2e 3af39644 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-mte KASAN: invalid-access Write in do_bad_area
* Struck through repros no longer work on HEAD.