================================================================== BUG: KASAN: invalid-access in __kvm_pgtable_visit arch/arm64/kvm/hyp/pgtable.c:163 [inline] BUG: KASAN: invalid-access in __kvm_pgtable_walk+0x8e4/0xa68 arch/arm64/kvm/hyp/pgtable.c:237 Read of size 8 at addr 65f0000020134000 by task syz.1.466/4970 Pointer tag: [65], memory tag: [fe] CPU: 0 UID: 0 PID: 4970 Comm: syz.1.466 Not tainted syzkaller #0 PREEMPT Hardware name: linux,dummy-virt (DT) Call trace: show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:499 (C) __dump_stack+0x30/0x40 lib/dump_stack.c:94 dump_stack_lvl+0xd8/0x12c lib/dump_stack.c:120 print_address_description+0xac/0x288 mm/kasan/report.c:378 print_report+0x84/0xa0 mm/kasan/report.c:482 kasan_report+0xb0/0x110 mm/kasan/report.c:595 kasan_tag_mismatch+0x28/0x3c mm/kasan/sw_tags.c:175 __hwasan_tag_mismatch+0x30/0x60 arch/arm64/lib/kasan_sw_tags.S:55 __kvm_pgtable_visit arch/arm64/kvm/hyp/pgtable.c:163 [inline] __kvm_pgtable_walk+0x8e4/0xa68 arch/arm64/kvm/hyp/pgtable.c:237 _kvm_pgtable_walk arch/arm64/kvm/hyp/pgtable.c:260 [inline] kvm_pgtable_walk+0x294/0x468 arch/arm64/kvm/hyp/pgtable.c:283 kvm_pgtable_stage2_destroy_range+0x60/0xb4 arch/arm64/kvm/hyp/pgtable.c:1563 stage2_destroy_range arch/arm64/kvm/mmu.c:924 [inline] kvm_stage2_destroy arch/arm64/kvm/mmu.c:935 [inline] kvm_free_stage2_pgd+0x198/0x28c arch/arm64/kvm/mmu.c:1112 kvm_uninit_stage2_mmu+0x20/0x38 arch/arm64/kvm/mmu.c:1023 kvm_arch_flush_shadow_all+0x1a8/0x1e0 arch/arm64/kvm/nested.c:1113 kvm_flush_shadow_all virt/kvm/kvm_main.c:343 [inline] kvm_mmu_notifier_release+0x48/0xa8 virt/kvm/kvm_main.c:884 mmu_notifier_unregister+0x128/0x42c mm/mmu_notifier.c:815 kvm_destroy_vm virt/kvm/kvm_main.c:1295 [inline] kvm_put_kvm+0x6a0/0xfa8 virt/kvm/kvm_main.c:1353 kvm_vcpu_release+0x70/0x9c virt/kvm/kvm_main.c:4100 __fput+0x4ac/0x980 fs/file_table.c:468 ____fput+0x20/0x58 fs/file_table.c:496 task_work_run+0x1bc/0x254 kernel/task_work.c:227 get_signal+0x13ec/0x1554 kernel/signal.c:2807 do_signal+0x23c/0x4dd0 arch/arm64/kernel/signal.c:1618 do_notify_resume+0xb0/0x270 arch/arm64/kernel/entry-common.c:152 exit_to_user_mode_prepare arch/arm64/kernel/entry-common.c:173 [inline] exit_to_user_mode arch/arm64/kernel/entry-common.c:182 [inline] el0_svc+0xb8/0x164 arch/arm64/kernel/entry-common.c:880 el0t_64_sync_handler+0x84/0x12c arch/arm64/kernel/entry-common.c:898 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:596 The buggy address belongs to the physical page: page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x60134 flags: 0x1ffe68000000000(node=0|zone=0|lastcpupid=0x7ff|kasantag=0x9a) raw: 01ffe68000000000 ffffc1ffc080c688 ffffc1ffc07ef0c8 0000000000000000 raw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000 page dumped because: kasan: bad access detected Memory state around the buggy address: fff0000020133e00: fe fe fe fe fe fe fe fe fe fe fe fe fe fe fe fe fff0000020133f00: fe fe fe fe fe fe fe fe fe fe fe fe fe fe fe fe >fff0000020134000: fe fe fe fe fe fe fe fe fe fe fe fe fe fe fe fe ^ fff0000020134100: fe fe fe fe fe fe fe fe fe fe fe fe fe fe fe fe fff0000020134200: fe fe fe fe fe fe fe fe fe fe fe fe fe fe fe fe ==================================================================