syzbot


KASAN: slab-out-of-bounds Read in data_sock_setsockopt

Status: upstream: reported C repro on 2026/02/27 14:00
Reported-by: syzbot+6091fa5ce6f8c7b38428@syzkaller.appspotmail.com
First crash: 5d12h, last: 5d01h
Bug presence (1)
Date Name Commit Repro Result
2026/02/28 upstream (ToT) 4d349ee5c778 C Failed due to an error; will retry later
Similar bugs (1)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream KASAN: slab-out-of-bounds Read in data_sock_setsockopt net 17 C 2 695d 695d 25/29 fixed on 2024/05/22 23:16

Sample crash report:
==================================================================
BUG: KASAN: slab-out-of-bounds in copy_from_sockptr_offset include/linux/sockptr.h:49 [inline]
BUG: KASAN: slab-out-of-bounds in copy_from_sockptr include/linux/sockptr.h:59 [inline]
BUG: KASAN: slab-out-of-bounds in data_sock_setsockopt+0x3a8/0x3d0 drivers/isdn/mISDN/socket.c:417
Read of size 4 at addr ffff0000ef19f603 by task syz.0.17/4503

CPU: 0 PID: 4503 Comm: syz.0.17 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/03/2025
Call trace:
 dump_backtrace+0x1c0/0x1ec arch/arm64/kernel/stacktrace.c:158
 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165
 __dump_stack+0x30/0x40 lib/dump_stack.c:88
 dump_stack_lvl+0xf4/0x15c lib/dump_stack.c:106
 print_address_description+0x88/0x218 mm/kasan/report.c:316
 print_report+0x50/0x68 mm/kasan/report.c:420
 kasan_report+0xa8/0xfc mm/kasan/report.c:524
 __asan_report_load_n_noabort+0x28/0x34 mm/kasan/report_generic.c:361
 copy_from_sockptr_offset include/linux/sockptr.h:49 [inline]
 copy_from_sockptr include/linux/sockptr.h:59 [inline]
 data_sock_setsockopt+0x3a8/0x3d0 drivers/isdn/mISDN/socket.c:417
 __sys_setsockopt+0x2fc/0x50c net/socket.c:2287
 __do_sys_setsockopt net/socket.c:2298 [inline]
 __se_sys_setsockopt net/socket.c:2295 [inline]
 __arm64_sys_setsockopt+0xb8/0xd4 net/socket.c:2295
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall+0x98/0x2b4 arch/arm64/kernel/syscall.c:52
 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
 do_el0_svc+0x58/0x130 arch/arm64/kernel/syscall.c:204
 el0_svc+0x58/0x128 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

Allocated by task 4503:
 kasan_save_stack mm/kasan/common.c:46 [inline]
 kasan_set_track+0x4c/0x80 mm/kasan/common.c:53
 kasan_save_alloc_info+0x24/0x30 mm/kasan/generic.c:505
 ____kasan_kmalloc mm/kasan/common.c:375 [inline]
 __kasan_kmalloc+0xa0/0xb8 mm/kasan/common.c:384
 kasan_kmalloc include/linux/kasan.h:211 [inline]
 __do_kmalloc_node mm/slab_common.c:936 [inline]
 __kmalloc+0xec/0x178 mm/slab_common.c:949
 kmalloc include/linux/slab.h:568 [inline]
 __cgroup_bpf_run_filter_setsockopt+0xa18/0xbe0 kernel/bpf/cgroup.c:1873
 __sys_setsockopt+0x4c0/0x50c net/socket.c:2270
 __do_sys_setsockopt net/socket.c:2298 [inline]
 __se_sys_setsockopt net/socket.c:2295 [inline]
 __arm64_sys_setsockopt+0xb8/0xd4 net/socket.c:2295
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall+0x98/0x2b4 arch/arm64/kernel/syscall.c:52
 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
 do_el0_svc+0x58/0x130 arch/arm64/kernel/syscall.c:204
 el0_svc+0x58/0x128 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 object at ffff0000ef19f600
 which belongs to the cache kmalloc-128 of size 128
The buggy address is located 3 bytes inside of
 128-byte region [ffff0000ef19f600, ffff0000ef19f680)

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

Memory state around the buggy address:
 ffff0000ef19f500: 00 00 00 00 fc fc fc fc fc fc fc fc fc fc fc fc
 ffff0000ef19f580: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
>ffff0000ef19f600: 03 fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
                   ^
 ffff0000ef19f680: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
 ffff0000ef19f700: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
==================================================================

Crashes (2):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/02/28 01:40 linux-6.1.y 779f9571ac3e 2cf092b8 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 KASAN: slab-out-of-bounds Read in data_sock_setsockopt
2026/02/27 13:59 linux-6.1.y 779f9571ac3e a2f13f71 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 KASAN: slab-out-of-bounds Read in data_sock_setsockopt
* Struck through repros no longer work on HEAD.