From: Phillip Potter <phil@philpotter.co.uk>
To: Jordy Zomer <jordyzomer@google.com>
Cc: linux-kernel@vger.kernel.org, linux-block@vger.kernel.org
Subject: Re: [PATCH v2 1/1] cdrom: Fix spectre-v1 gadget
Date: Thu, 15 Jun 2023 09:12:33 +0100 [thread overview]
Message-ID: <ZIrH8fMomznQWZGj@equinox> (raw)
In-Reply-To: <20230612110040.849318-2-jordyzomer@google.com>
On Mon, Jun 12, 2023 at 11:00:40AM +0000, Jordy Zomer wrote:
> This patch fixes a spectre-v1 gadget in cdrom.
> The gadget could be triggered by,
> speculatviely bypassing the cdi->capacity check.
>
> Signed-off-by: Jordy Zomer <jordyzomer@google.com>
> ---
> drivers/cdrom/cdrom.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/cdrom/cdrom.c b/drivers/cdrom/cdrom.c
> index 416f723a2dbb..ecf2b458c108 100644
> --- a/drivers/cdrom/cdrom.c
> +++ b/drivers/cdrom/cdrom.c
> @@ -264,6 +264,7 @@
> #include <linux/errno.h>
> #include <linux/kernel.h>
> #include <linux/mm.h>
> +#include <linux/nospec.h>
> #include <linux/slab.h>
> #include <linux/cdrom.h>
> #include <linux/sysctl.h>
> @@ -2329,6 +2330,9 @@ static int cdrom_ioctl_media_changed(struct cdrom_device_info *cdi,
> if (arg >= cdi->capacity)
> return -EINVAL;
>
> + /* Prevent arg from speculatively bypassing the length check */
> + barrier_nospec();
> +
> info = kmalloc(sizeof(*info), GFP_KERNEL);
> if (!info)
> return -ENOMEM;
> --
> 2.41.0.162.gfafddb0af9-goog
>
Hi Jordy,
Thanks for the patch, I will review/build it properly tonight after
work, although at first glance it looks good to me. I'll be in touch.
Regards,
Phil Potter
next prev parent reply other threads:[~2023-06-15 8:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 11:00 [PATCH v2 0/1] cdrom: Fix spectre-v1 gadget Jordy Zomer
2023-06-12 11:00 ` [PATCH v2 1/1] " Jordy Zomer
2023-06-15 8:12 ` Phillip Potter [this message]
2023-06-15 16:31 ` Pawan Gupta
2023-06-15 23:31 ` Phillip Potter
2023-06-16 3:14 ` Pawan Gupta
2023-06-16 9:39 ` Jordy Zomer
2023-06-16 12:59 ` Randy Dunlap
2023-06-17 9:40 ` Phillip Potter
2023-06-17 9:37 ` Phillip Potter
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=ZIrH8fMomznQWZGj@equinox \
--to=phil@philpotter.co.uk \
--cc=jordyzomer@google.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox