From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Jeremy Cline <jcline@redhat.com>
Cc: Theodore Ts'o <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH 1/3] ext4: super: Fix spectre gadget in ext4_quota_on
Date: Fri, 27 Jul 2018 12:46:54 -0500 [thread overview]
Message-ID: <20180727174654.bnooz26puuo7456w@treble> (raw)
In-Reply-To: <20180727162357.30801-2-jcline@redhat.com>
On Fri, Jul 27, 2018 at 04:23:55PM +0000, Jeremy Cline wrote:
> 'type' is a user-controlled value used to index into 's_qf_names', which
> can be used in a Spectre v1 attack. Clamp 'type' to the size of the
> array to avoid a speculative out-of-bounds read.
>
> Cc: Josh Poimboeuf <jpoimboe@redhat.com>
> Cc: stable@vger.kernel.org
> Signed-off-by: Jeremy Cline <jcline@redhat.com>
> ---
> fs/ext4/super.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/fs/ext4/super.c b/fs/ext4/super.c
> index 6480e763080f..c04a09b51742 100644
> --- a/fs/ext4/super.c
> +++ b/fs/ext4/super.c
> @@ -40,6 +40,7 @@
> #include <linux/crc16.h>
> #include <linux/dax.h>
> #include <linux/cleancache.h>
> +#include <linux/nospec.h>
> #include <linux/uaccess.h>
> #include <linux/iversion.h>
>
> @@ -5559,6 +5560,7 @@ static int ext4_quota_on(struct super_block *sb, int type, int format_id,
> if (path->dentry->d_sb != sb)
> return -EXDEV;
> /* Journaling quota? */
> + type = array_index_nospec(type, EXT4_MAXQUOTAS);
> if (EXT4_SB(sb)->s_qf_names[type]) {
> /* Quotafile not in fs root? */
> if (path->dentry->d_parent != sb->s_root)
Generally we try to put the array_index_nospec() close to the bounds
check for which it's trying to prevent speculation past.
In this case, I'd expect the EXT4_MAXQUOTAS bounds check to be in
do_quotactl(), but it seems to be missing:
if (type >= (XQM_COMMAND(cmd) ? XQM_MAXQUOTAS : MAXQUOTAS))
return -EINVAL;
Also it looks like XQM_MAXQUOTAS, MAXQUOTAS, and EXT4_MAXQUOTAS all have
the same value (3). Maybe they can be consolidated to just use
MAXQUOTAS everywhere? Then the nospec would be simple:
if (type >= MAXQUOTAS)
return -EINVAL;
type = array_index_nospec(type, MAXQUOTAS);
Otherwise I think we may need to disperse the array_index_nospec calls
deeper in the callchain.
--
Josh
next prev parent reply other threads:[~2018-07-27 19:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180727162357.30801-1-jcline@redhat.com>
2018-07-27 16:23 ` [PATCH 1/3] ext4: super: Fix spectre gadget in ext4_quota_on Jeremy Cline
2018-07-27 17:46 ` Josh Poimboeuf [this message]
2018-07-27 19:17 ` Jeremy Cline
2018-07-31 6:39 ` Andreas Dilger
2018-07-31 17:31 ` Josh Poimboeuf
2018-07-27 16:23 ` [PATCH 2/3] ext4: super: Fix spectre gadgets in ext4_quota_{read,write,off} Jeremy Cline
2018-07-27 16:23 ` [PATCH 3/3] ext4: mballoc: Fix spectre gadget in ext4_mb_simple_scan_group Jeremy Cline
2018-07-27 18:10 ` Josh Poimboeuf
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=20180727174654.bnooz26puuo7456w@treble \
--to=jpoimboe@redhat.com \
--cc=adilger.kernel@dilger.ca \
--cc=jcline@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tytso@mit.edu \
/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