linux-kernel - Re: CVE-2021-46978: KVM: nVMX: Always make an attempt to map eVMCS after migration

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: <20240229143454.GC272762@mit.edu>
Date: Thu, 29 Feb 2024 08:34:54 -0600
From: "Theodore Ts'o" <tytso@....edu>
To: Paolo Bonzini <pbonzini@...hat.com>
Cc: Greg KH <gregkh@...nel.org>, cve@...nel.org, linux-kernel@...r.kernel.org,
        KVM list <kvm@...r.kernel.org>, Vitaly Kuznetsov <vkuznets@...hat.com>
Subject: Re: CVE-2021-46978: KVM: nVMX: Always make an attempt to map eVMCS
 after migration

On Thu, Feb 29, 2024 at 11:04:45AM +0100, Paolo Bonzini wrote:
> Also, LKML does not get the initial announcement, which makes it a bit
> more painful to find the full discussion on lore (you have to go
> through a "no message with that id, maybe you mean this one from other
> mailing lists" page, instead of having the whole thread in the same
> place). A linux-cve mailing list with public posting, used for Cc and
> Reply-to of the initial message, would solve this issue as well.

I believe the url https://lore.kernel.org/all/<message-id> will get
the whole thread, regardless of which mailing lists individual mail
messages were sent to, does it not?

					- Ted