================================================================================
UBSAN: Undefined behaviour in arch/x86/kvm/pmu_intel.c:299:45
shift exponent 134 is too large for 64-bit type 'long long unsigned int'
CPU: 1 PID: 13450 Comm: syz-executor.2 Not tainted 4.19.152-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 __dump_stack lib/dump_stack.c:77 [inline]
 dump_stack+0x22c/0x33e lib/dump_stack.c:118
 ubsan_epilogue+0xe/0x3a lib/ubsan.c:161
 __ubsan_handle_shift_out_of_bounds.cold+0x1c4/0x250 lib/ubsan.c:422
 intel_pmu_refresh.cold+0x9b/0xa0 arch/x86/kvm/pmu_intel.c:299
 kvm_update_cpuid+0x6d9/0xaf0 arch/x86/kvm/cpuid.c:147
 kvm_vcpu_ioctl_set_cpuid+0x6ab/0x970 arch/x86/kvm/cpuid.c:232
 kvm_arch_vcpu_ioctl+0xea3/0x2e10 arch/x86/kvm/x86.c:3921
 kvm_vcpu_ioctl+0x8af/0xe30 arch/x86/kvm/../../../virt/kvm/kvm_main.c:2975
 vfs_ioctl fs/ioctl.c:46 [inline]
 file_ioctl fs/ioctl.c:501 [inline]
 do_vfs_ioctl+0xcdb/0x12e0 fs/ioctl.c:688
 ksys_ioctl+0x9b/0xc0 fs/ioctl.c:705
 __do_sys_ioctl fs/ioctl.c:712 [inline]
 __se_sys_ioctl fs/ioctl.c:710 [inline]
 __x64_sys_ioctl+0x6f/0xb0 fs/ioctl.c:710
 do_syscall_64+0xf9/0x670 arch/x86/entry/common.c:293
 entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x45de59
Code: 0d b4 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 0f 83 db b3 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f2c3a6fac78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000011f00 RCX: 000000000045de59
RDX: 0000000020000380 RSI: 000000004008ae8a RDI: 0000000000000005
RBP: 000000000118bf60 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000118bf2c
R13: 00007ffc33b94f5f R14: 00007f2c3a6fb9c0 R15: 000000000118bf2c
================================================================================
================================================================================
UBSAN: Undefined behaviour in arch/x86/kvm/pmu_intel.c:301:13
shift exponent 113 is too large for 64-bit type 'long long unsigned int'
CPU: 0 PID: 13451 Comm: syz-executor.1 Not tainted 4.19.152-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 __dump_stack lib/dump_stack.c:77 [inline]
 dump_stack+0x22c/0x33e lib/dump_stack.c:118
 ubsan_epilogue+0xe/0x3a lib/ubsan.c:161
 __ubsan_handle_shift_out_of_bounds.cold+0x1c4/0x250 lib/ubsan.c:422
 intel_pmu_refresh.cold+0x75/0xa0 arch/x86/kvm/pmu_intel.c:301
 kvm_update_cpuid+0x6d9/0xaf0 arch/x86/kvm/cpuid.c:147
 kvm_vcpu_ioctl_set_cpuid+0x6ab/0x970 arch/x86/kvm/cpuid.c:232
 kvm_arch_vcpu_ioctl+0xea3/0x2e10 arch/x86/kvm/x86.c:3921
 kvm_vcpu_ioctl+0x8af/0xe30 arch/x86/kvm/../../../virt/kvm/kvm_main.c:2975
 vfs_ioctl fs/ioctl.c:46 [inline]
 file_ioctl fs/ioctl.c:501 [inline]
 do_vfs_ioctl+0xcdb/0x12e0 fs/ioctl.c:688
 ksys_ioctl+0x9b/0xc0 fs/ioctl.c:705
 __do_sys_ioctl fs/ioctl.c:712 [inline]
 __se_sys_ioctl fs/ioctl.c:710 [inline]
 __x64_sys_ioctl+0x6f/0xb0 fs/ioctl.c:710
 do_syscall_64+0xf9/0x670 arch/x86/entry/common.c:293
 entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x45de59
Code: 0d b4 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 0f 83 db b3 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f955fbb2c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000011f00 RCX: 000000000045de59
RDX: 0000000020000380 RSI: 000000004008ae8a RDI: 0000000000000005
RBP: 000000000118bf60 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000118bf2c
R13: 00007ffd5bdbb42f R14: 00007f955fbb39c0 R15: 000000000118bf2c
================================================================================
netlink: 512 bytes leftover after parsing attributes in process `syz-executor.4'.
encrypted_key: key user:syz not found
syz-executor.1 uses obsolete (PF_INET,SOCK_PACKET)
EXT4-fs (loop4): VFS: Can't find ext4 filesystem
EXT4-fs (loop4): VFS: Can't find ext4 filesystem
TCP: request_sock_TCPv6: Possible SYN flooding on port 20002. Sending cookies.  Check SNMP counters.
audit: type=1804 audit(1603074645.188:14): pid=13935 uid=0 auid=0 ses=4 subj=system_u:system_r:kernel_t:s0 op=invalid_pcr cause=open_writers comm="syz-executor.1" name="/root/syzkaller-testdir539077479/syzkaller.NL7xw4/465/file1/file0" dev="loop1" ino=3 res=1
FAT-fs (loop4): Directory bread(block 6) failed
audit: type=1804 audit(1603074645.368:15): pid=13955 uid=0 auid=0 ses=4 subj=system_u:system_r:kernel_t:s0 op=invalid_pcr cause=open_writers comm="syz-executor.5" name="/root/syzkaller-testdir994660612/syzkaller.frs4BK/481/file1/file0" dev="loop5" ino=4 res=1
audit: type=1804 audit(1603074645.628:16): pid=13978 uid=0 auid=0 ses=4 subj=system_u:system_r:kernel_t:s0 op=invalid_pcr cause=open_writers comm="syz-executor.2" name="/root/syzkaller-testdir527876060/syzkaller.e4o4ia/461/file1/file0" dev="loop2" ino=5 res=1
F2FS-fs (loop5): Magic Mismatch, valid(0xf2f52010) - read(0x0)
F2FS-fs (loop5): Can't find valid F2FS filesystem in 2th superblock
F2FS-fs (loop5): invalid crc value
F2FS-fs (loop5): Found nat_bits in checkpoint
F2FS-fs (loop5): Try to recover 2th superblock, ret: 0
F2FS-fs (loop5): Mounted with checkpoint version = cabf473
audit: type=1804 audit(1603074646.178:17): pid=14021 uid=0 auid=0 ses=4 subj=system_u:system_r:kernel_t:s0 op=invalid_pcr cause=open_writers comm="syz-executor.3" name="/root/syzkaller-testdir743758837/syzkaller.6STTgm/482/file1/file0" dev="loop3" ino=6 res=1
audit: type=1804 audit(1603074646.368:18): pid=14034 uid=0 auid=0 ses=4 subj=system_u:system_r:kernel_t:s0 op=invalid_pcr cause=open_writers comm="syz-executor.1" name="/root/syzkaller-testdir539077479/syzkaller.NL7xw4/470/file1/file0" dev="loop1" ino=7 res=1
EXT4-fs (loop4): mounted filesystem without journal. Opts: ,errors=continue
EXT4-fs (loop2): mounted filesystem without journal. Opts: ,errors=continue
EXT4-fs error (device loop2): ext4_empty_dir:2739: inode #12: block 255: comm syz-executor.2: bad entry in directory: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0, size=1024
EXT4-fs warning (device loop2): ext4_empty_dir:2742: inode #12: comm syz-executor.2: directory missing '.'
EXT4-fs error (device loop2): ext4_validate_block_bitmap:392: comm syz-executor.2: bg 0: block 3: invalid block bitmap
EXT4-fs error (device loop2) in ext4_free_blocks:4971: Corrupt filesystem
EXT4-fs error (device loop2): ext4_free_inode:350: comm syz-executor.2: bit already cleared for inode 12
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=0 sclass=netlink_route_socket pid=14124 comm=syz-executor.5
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=0 sclass=netlink_route_socket pid=14130 comm=syz-executor.5