KASAN: user-memory-access Read in kvmclock_cpufreq_notifier

Status: closed as dup on 2020/08/16 04:05
Subsystems: kvm-x86
[Documentation on labels]
Reported-by: syzbot+59cd93bc8960efdbae86@syzkaller.appspotmail.com
First crash: 2333d, last: 2303d
Cause bisection: the issue happens on the oldest tested release (bisect log)
Crash: WARNING in sysfs_warn_dup (log)
Repro: C syz .config
  
Fix bisection: failed (error log, bisect log)
  
▶ ▼ Duplicate of
Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported
general protection fault in syscall_return_slowpath kernel 2 syz inconclusive done 1 2251d 2337d
▶ ▼ Discussions (1)
Title Replies (including bot) Last reply
KASAN: user-memory-access Read in kvmclock_cpufreq_notifier 0 (1) 2020/03/16 14:07
▶ ▼ Fix bisection attempts (2)
Created Duration User Patch Repo Result
2020/05/11 14:30 0m bisect fix upstream error job log
2020/04/11 14:00 29m bisect fix upstream OK (0) job log log

Sample crash report:
==================================================================
BUG: KASAN: user-memory-access in atomic_read include/asm-generic/atomic-instrumented.h:26 [inline]
BUG: KASAN: user-memory-access in __kvmclock_cpufreq_notifier arch/x86/kvm/x86.c:7133 [inline]
BUG: KASAN: user-memory-access in kvmclock_cpufreq_notifier+0x1e9/0x580 arch/x86/kvm/x86.c:7172
Read of size 4 at addr 00000000896bb8f0 by task syz-executor372/10372

CPU: 0 PID: 10372 Comm: syz-executor372 Not tainted 5.6.0-rc5-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 <IRQ>
 __dump_stack lib/dump_stack.c:77 [inline]
 dump_stack+0x188/0x20d lib/dump_stack.c:118
 __kasan_report.cold+0x5/0x32 mm/kasan/report.c:510
 kasan_report+0xe/0x20 mm/kasan/common.c:641
 check_memory_region_inline mm/kasan/generic.c:185 [inline]
 check_memory_region+0x128/0x190 mm/kasan/generic.c:192
 atomic_read include/asm-generic/atomic-instrumented.h:26 [inline]
 __kvmclock_cpufreq_notifier arch/x86/kvm/x86.c:7133 [inline]
 kvmclock_cpufreq_notifier+0x1e9/0x580 arch/x86/kvm/x86.c:7172
 </IRQ>
==================================================================
Kernel panic - not syncing: panic_on_warn set ...
CPU: 0 PID: 10372 Comm: syz-executor372 Tainted: G    B             5.6.0-rc5-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 <IRQ>
 __dump_stack lib/dump_stack.c:77 [inline]
 dump_stack+0x188/0x20d lib/dump_stack.c:118
 panic+0x2e3/0x75c kernel/panic.c:221
 end_report+0x43/0x49 mm/kasan/report.c:96
 __kasan_report.cold+0xd/0x32 mm/kasan/report.c:513
 kasan_report+0xe/0x20 mm/kasan/common.c:641
 check_memory_region_inline mm/kasan/generic.c:185 [inline]
 check_memory_region+0x128/0x190 mm/kasan/generic.c:192
 atomic_read include/asm-generic/atomic-instrumented.h:26 [inline]
 __kvmclock_cpufreq_notifier arch/x86/kvm/x86.c:7133 [inline]
 kvmclock_cpufreq_notifier+0x1e9/0x580 arch/x86/kvm/x86.c:7172
 </IRQ>
Shutting down cpus with NMI
Kernel Offset: disabled
Rebooting in 86400 seconds..

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2020/03/12 13:58 upstream e6e6ec48dd0f d850e9d0 .config console log report syz C ci-upstream-kasan-gce-selinux-root
* Struck through repros no longer work on HEAD.