linux-kernel - ITLB Multihit mitigation status report is confusing.

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

Message-Id: <6D53FB74-4B6C-48A0-97BB-300A9C81B55C@gmail.com>
Date:   Sun, 7 Nov 2021 19:00:36 +0300
From:   Lucius User <lucius.q.user@...il.com>
To:     linux-kernel@...r.kernel.org
Subject: ITLB Multihit mitigation status report is confusing. 

Hi all. 

On a cpu that is vulnerable to iTLB multihit, with VMX enabled in bios and no vms running, the kernel reports the mitigation status as "KVM: Mitigation: VMX disabled". Once a vm starts running, the report changes to "KVM: Vulnerable". Shouldn't the VMX disabled status refer to a situation when VMX is completely disabled via bios, not merely not in use right now?