From: Greg KH <gregkh@linuxfoundation.org>
To: Hagar Gamal Halim Hemdan <hagarhem@amazon.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] vmci: prevent speculation leaks by sanitizing event in event_deliver()
Date: Mon, 27 Nov 2023 18:47:41 +0000 [thread overview]
Message-ID: <2023112728-footless-overkill-3732@gregkh> (raw)
In-Reply-To: <20231127183745.94955-1-hagarhem@amazon.com>
On Mon, Nov 27, 2023 at 06:37:45PM +0000, Hagar Gamal Halim Hemdan wrote:
> Coverity spotted that event_msg is controlled by user-space,
> event_msg->event_data.event is passed to event_deliver() and used
> as an index without sanitization.
>
> This change ensures that the event index is sanitized to mitigate any
> possibility of speculative information leaks.
>
> Fixes: 1d990201f9bb ("VMCI: event handling implementation")
>
> Signed-off-by: Hagar Gamal Halim Hemdan <hagarhem@amazon.com>
> ---
> drivers/misc/vmw_vmci/vmci_event.c | 6 +++++-
: 1 file changed, 5 insertions(+), 1 deletion(-)
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.
</formletter>
next prev parent reply other threads:[~2023-11-27 18:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 18:37 [PATCH] vmci: prevent speculation leaks by sanitizing event in event_deliver() Hagar Gamal Halim Hemdan
2023-11-27 18:47 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-27 19:35 Hagar Gamal Halim Hemdan
2023-11-27 19:35 ` Hagar Gamal Halim Hemdan
2023-11-27 19:41 ` kernel test robot
2023-11-27 19:48 Hagar Gamal Halim Hemdan
2023-11-27 19:48 ` Hagar Gamal Halim Hemdan
2023-11-28 8:09 ` Greg Kroah-Hartman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2023112728-footless-overkill-3732@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=hagarhem@amazon.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.