KASAN: out-of-bounds Read in unwind_next

Kernel	Title	Repro	Cause bisect	Fix bisect	Count	Last	Reported	Patched	Status
upstream	KASAN: out-of-bounds Read in unwind_next_frame fs	syz	error	error	12	1663d	1928d	0/26	auto-obsoleted due to no activity on 2022/09/07 09:08
linux-4.19	KASAN: out-of-bounds Read in unwind_next_frame				1	1610d	1610d	0/1	auto-closed as invalid on 2020/03/19 23:00
linux-4.19	KASAN: stack-out-of-bounds Read in unwind_next_frame	C		error	525	427d	1512d	0/1	upstream: reported C repro on 2020/02/26 18:51
upstream	KASAN: stack-out-of-bounds Read in unwind_next_frame kernel	C			929	392d	2129d	0/26	closed as dup on 2018/06/20 07:51
android-49	KASAN: out-of-bounds Read in unwind_next_frame	C			14	2016d	1832d	0/3	public: reported C repro on 2019/04/13 00:00
android-54	KASAN: out-of-bounds Read in unwind_next_frame				16	946d	1452d	0/2	auto-closed as invalid on 2022/01/13 05:16
linux-4.19	KASAN: out-of-bounds Read in unwind_next_frame (2)				1	1199d	1199d	0/1	auto-closed as invalid on 2021/05/04 22:57
android-414	KASAN: out-of-bounds Read in unwind_next_frame (2)	C			5	1605d	1712d	0/1	public: reported C repro on 2019/08/11 14:38
android-414	KASAN: out-of-bounds Read in unwind_next_frame				1	2009d	1831d	0/1	auto-closed as invalid on 2019/04/28 00:03

Created	Duration	User	Patch	Repo	Result
2023/01/30 13:32	11m	retest repro		linux-4.14.y	report log
2022/09/10 11:27	8m	retest repro		linux-4.14.y	report log

Created

Duration

User

Patch

Repo

Result

2023/01/30 13:32

11m

retest repro

linux-4.14.y

report log

2022/09/10 11:27

retest repro

linux-4.14.y

report log

================================================================== BUG: KASAN: out-of-bounds in unwind_next_frame.part.0+0x627/0x8b0 arch/x86/kernel/unwind_frame.c:291 Read of size 8 at addr ffff8880988df9f0 by task syz-executor280/10550 CPU: 0 PID: 10550 Comm: syz-executor280 Not tainted 4.14.160-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: __dump_stack lib/dump_stack.c:17 [inline] dump_stack+0x142/0x197 lib/dump_stack.c:58 print_address_description.cold+0x7c/0x1dc mm/kasan/report.c:252 kasan_report_error mm/kasan/report.c:351 [inline] kasan_report mm/kasan/report.c:409 [inline] kasan_report.cold+0xa9/0x2af mm/kasan/report.c:393 __asan_report_load8_noabort+0x14/0x20 mm/kasan/report.c:430 unwind_next_frame.part.0+0x627/0x8b0 arch/x86/kernel/unwind_frame.c:291 unwind_next_frame+0x3b/0x50 arch/x86/kernel/unwind_frame.c:287 __save_stack_trace+0x6b/0xd0 arch/x86/kernel/stacktrace.c:44 save_stack_trace_tsk arch/x86/kernel/stacktrace.c:73 [inline] save_stack_trace_tsk+0x3e/0x50 arch/x86/kernel/stacktrace.c:68 proc_pid_stack+0x174/0x250 fs/proc/base.c:459 proc_single_show+0xf0/0x160 fs/proc/base.c:761 seq_read+0x51a/0x1280 fs/seq_file.c:237 do_loop_readv_writev fs/read_write.c:695 [inline] do_loop_readv_writev fs/read_write.c:682 [inline] do_iter_read+0x3e2/0x5b0 fs/read_write.c:919 vfs_readv+0xd3/0x130 fs/read_write.c:981 do_preadv+0x15d/0x200 fs/read_write.c:1065 SYSC_preadv fs/read_write.c:1115 [inline] SyS_preadv+0x31/0x40 fs/read_write.c:1110 do_syscall_64+0x1e8/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x42/0xb7 RIP: 0033:0x448c19 RSP: 002b:00007f101edeed08 EFLAGS: 00000246 ORIG_RAX: 0000000000000127 RAX: ffffffffffffffda RBX: 00000000006dec68 RCX: 0000000000448c19 RDX: 000000000000022a RSI: 00000000200017c0 RDI: 0000000000000004 RBP: 00000000006dec60 R08: 65732f636f72702f R09: 65732f636f72702f R10: 0000000000000000 R11: 0000000000000246 R12: 00000000006dec6c R13: 00007f101edeed10 R14: 00007f101edeed10 R15: 0000000030626669 The buggy address belongs to the page: page:ffffea00026237c0 count:0 mapcount:0 mapping: (null) index:0x0 flags: 0xfffe0000000000() raw: 00fffe0000000000 0000000000000000 0000000000000000 00000000ffffffff raw: 0000000000000000 0000000100000001 0000000000000000 0000000000000000 page dumped because: kasan: bad access detected Memory state around the buggy address: ffff8880988df880: 00 00 00 00 00 00 00 f1 f1 f1 f1 00 00 f3 f3 00 ffff8880988df900: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ffff8880988df980: f1 f1 f1 f1 00 00 00 f2 f2 f2 00 00 00 00 00 00 ^ ffff8880988dfa00: 00 00 00 00 f3 f3 f3 f3 00 00 00 00 00 00 00 00 ffff8880988dfa80: 00 00 00 00 00 f1 f1 f1 f1 f1 f1 00 00 00 00 00 ==================================================================

Time	Kernel	Commit	Syzkaller	Config	Log	Report	Syz repro	C repro	Manager
2019/12/29 18:08	linux-4.14.y	e1f7d50ae3a3	af6b8ef8	.config	console log	report	syz	C	ci2-linux-4-14
2020/08/26 12:17	linux-4.14.y	d7e78d08fa77	318430cb	.config	console log	report			ci2-linux-4-14
2020/08/17 14:52	linux-4.14.y	14b58326976d	5ce13532	.config	console log	report			ci2-linux-4-14
2020/07/29 16:02	linux-4.14.y	e5a54aa2d312	19a8de55	.config	console log	report			ci2-linux-4-14
2020/07/24 09:12	linux-4.14.y	69b94dd6dcd1	70c104a1	.config	console log	report			ci2-linux-4-14
2020/05/26 09:47	linux-4.14.y	a41ba30d9df2	8ca3b7d2	.config	console log	report			ci2-linux-4-14
2020/05/22 00:32	linux-4.14.y	a41ba30d9df2	4afdfa20	.config	console log	report			ci2-linux-4-14
2020/05/11 08:05	linux-4.14.y	ab9dfda23248	f8f57555	.config	console log	report			ci2-linux-4-14
2020/05/06 23:09	linux-4.14.y	d71f695ce745	4618eb2d	.config	console log	report			ci2-linux-4-14
2020/03/27 10:49	linux-4.14.y	01364dad1d45	9af8b4b3	.config	console log	report			ci2-linux-4-14
2020/03/24 05:53	linux-4.14.y	01364dad1d45	33e14df3	.config	console log	report			ci2-linux-4-14
2020/01/16 19:27	linux-4.14.y	c04fc6fa5c96	3de7aabb	.config	console log	report			ci2-linux-4-14
2019/10/04 06:01	linux-4.14.y	f6e27dbb1afa	fc17ba49	.config	console log	report			ci2-linux-4-14
2019/09/26 20:19	linux-4.14.y	f6e27dbb1afa	2f1548bc	.config	console log	report			ci2-linux-4-14