linux-kernel - Re: [GIT PULL] KVM/x86 changes for Linux 6.12

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CABgObfYCBOjDwFfi3-k1ddRLKQ691DP-pnKMBzDGE3Dt9YFwNQ@mail.gmail.com>
Date: Sat, 28 Sep 2024 19:19:05 +0200
From: Paolo Bonzini <pbonzini@...hat.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: linux-kernel@...r.kernel.org, kvm@...r.kernel.org
Subject: Re: [GIT PULL] KVM/x86 changes for Linux 6.12

On Sat, Sep 28, 2024 at 6:30 PM Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> On Sat, 28 Sept 2024 at 08:33, Paolo Bonzini <pbonzini@...hat.com> wrote:
> >
> > Apologize for the late pull request; all the traveling made things a
> > bit messy.  Also, we have a known regression here on ancient processors
> > and will fix it next week.
>
> Gaah. Don't leave it hanging like that. When somebody reports a
> problem, I need to know if it's this known one.
> I've pulled it, but you really need to add a pointer to "look, this is
> the known one, we have a fix in the works"

If that's what you mean, it was not reported by users (and it's very
unlikely that it will, unless they run selftests on pre-2008
processors or with non-standard module parameters). It's a NULL
pointer dereference on VM shutdown, caused by the selftests added by
commit b4ed2c67d275 ("KVM: selftests: Test slot move/delete with slot
zap quirk enabled/disabled").

It's also not reproducible yet outside selftests since the bug is in a
new API; which is also why we didn't revert with prejudice and didn't
go too much into detail above.

Paolo