linux-kernel - Re: [PATCH] x86/vmware: Fix hypercall clobbers

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: <cwxcn2oufcpvzenyicg27umr3gbuow26ufotfhck6vauxyqmam@e6ssitydnafx>
Date: Fri, 6 Feb 2026 16:46:11 -0800
From: Josh Poimboeuf <jpoimboe@...nel.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Paolo Bonzini <pbonzini@...hat.com>, Thomas Gleixner <tglx@...-um.de>, 
	Thorsten Leemhuis <regressions@...mhuis.info>, Alexey Makhalov <alexey.makhalov@...adcom.com>, x86@...nel.org, 
	linux-kernel@...r.kernel.org, Ajay Kaher <ajay.kaher@...adcom.com>, 
	bcm-kernel-feedback-list@...adcom.com, Peter Zijlstra <peterz@...radead.org>, 
	Justin Forbes <jforbes@...oraproject.org>, Linux kernel regressions list <regressions@...ts.linux.dev>
Subject: Re: [PATCH] x86/vmware: Fix hypercall clobbers

On Fri, Feb 06, 2026 at 03:08:29PM -0800, Linus Torvalds wrote:
> On Fri, 6 Feb 2026 at 14:38, Linus Torvalds
> <torvalds@...ux-foundation.org> wrote:
> >
> > I'm going to change that commit message to make it clear that it's a
> > QEMU bug, plain and simple. There's no point in claiming this fixes a
> > kernel bug when it's a pure workaround for a bug elsewhere.
> 
> I have created an issue at gitlab:
> 
>    https://gitlab.com/qemu-project/qemu/-/issues/3293
> 
> and hopefully this will get fixed in QEMU at some point.
> 
> Adding Paolo to the participants, since he presumably knows what to do
> with qemu, since he touched that qemu file a couple of months ago.
> 
> (The fix looks trivial, as suggested by Alexey: just change the
> "uint32_t data[6];" to use target_ulong instead of uint32_t, but
> somebody needs to test it and maybe qemu has other rules for register
> types)

I posted a QEMU fix here:

  https://lists.gnu.org/archive/html/qemu-devel/2026-02/msg01713.html

(using uint64_t instead of target_ulong at the maintainer's request as
they are phasing out the target_ulong type).

-- 
Josh