linux-kernel - Re: WARNING in kvm_mmu_uninit_tdp

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <Yd3cjllVD4vS17kG@google.com>
Date:   Tue, 11 Jan 2022 19:37:50 +0000
From:   Sean Christopherson <seanjc@...gle.com>
To:     "Sabri N. Ferreiro" <snferreiro1@...il.com>
Cc:     Paolo Bonzini <pbonzini@...hat.com>,
        Vitaly Kuznetsov <vkuznets@...hat.com>,
        Wanpeng Li <wanpengli@...cent.com>,
        Jim Mattson <jmattson@...gle.com>,
        Joerg Roedel <joro@...tes.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
        Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org,
        "H. Peter Anvin" <hpa@...or.com>, kvm@...r.kernel.org,
        linux-kernel@...r.kernel.org, sunhao.th@...il.com
Subject: Re: WARNING in kvm_mmu_uninit_tdp_mmu

On Sun, Jan 09, 2022, Sabri N. Ferreiro wrote:
> Hi,
> 
> When using Syzkaller to fuzz the Linux kernel, it triggers the following crash.
> 
> HEAD commit: a7904a538933 Linux 5.16-rc6
> git tree: upstream
> console output: https://pastebin.com/raw/keWCUeJ2
> kernel config: https://docs.google.com/document/d/1w94kqQ4ZSIE6BW-5WIhqp4_Zh7XTPH57L5OF2Xb6O6o/view
> C reproducer: https://pastebin.com/raw/kSxa6Yit
> Syzlang reproducer: https://pastebin.com/raw/2RMu8p6E
> 
> If you fix this issue, please add the following tag to the commit:
> Reported-by: Yuheng Shen mosesfonscqf75@...il.com
> 
> ------------[ cut here ]------------
> WARNING: CPU: 5 PID: 29657 at arch/x86/kvm/mmu/tdp_mmu.c:46
> kvm_mmu_uninit_tdp_mmu+0xb9/0xf0

I wasn't able to reproduce to confirm, but this is more than likely fixed by
commit 3a0f64de479c ("KVM: x86/mmu: Don't advance iterator after restart due to yielding"),
which didn't land until 5.16-rc7.