[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240625084721.GCZnqEGbrkNNW6ZCfZ@fat_crate.local>
Date: Tue, 25 Jun 2024 10:47:21 +0200
From: Borislav Petkov <bp@...en8.de>
To: Alexey Makhalov <alexey.makhalov@...adcom.com>
Cc: linux-kernel@...r.kernel.org, virtualization@...ts.linux.dev,
hpa@...or.com, dave.hansen@...ux.intel.com, mingo@...hat.com,
tglx@...utronix.de, x86@...nel.org, ajay.kaher@...adcom.com,
bcm-kernel-feedback-list@...adcom.com,
Alex James <alex.james@...adcom.com>
Subject: Re: [PATCH] x86/vmware: fix panic in vmware_hypercall_slow()
On Tue, Jun 25, 2024 at 01:33:48AM -0700, Alexey Makhalov wrote:
> Caller of vmware_hypercall_slow() can pass NULL into *out1,
> *out2,... *out5. It will lead to a NULL pointer dereference.
>
> Check a pointer for NULL before assigning a value.
I queue your patches and *now* you find this?!
How did you test them in the first place and why was this scenario missed?
Geez.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists