From: Greg KH <gregkh@linuxfoundation.org>
To: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
Cc: scott.d.constable@intel.com, daniel.sneddon@linux.intel.com,
Jakub Kicinski <kuba@kernel.org>,
dave.hansen@intel.com, Johannes Berg <johannes@sipsolutions.net>,
Paolo Abeni <pabeni@redhat.com>,
antonio.gomez.iglesias@linux.intel.com,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
x86@kernel.org, netdev@vger.kernel.org
Subject: Re: [RFC PATCH 2/2] minstrel_ht: Mitigate BTI gadget minstrel_ht_get_expected_throughput()
Date: Tue, 25 Oct 2022 09:36:56 +0200 [thread overview]
Message-ID: <Y1eSGK5vylNmBbVp@kroah.com> (raw)
In-Reply-To: <ceb2bcdc79f1494151e85734fa7bdc639df275bb.1666651511.git.pawan.kumar.gupta@linux.intel.com>
On Mon, Oct 24, 2022 at 03:57:47PM -0700, Pawan Gupta wrote:
> Static analysis indicate that indirect target
> minstrel_ht_get_expected_throughput() could be used as a disclosure
> gadget for Intra-mode Branch Target Injection (IMBTI) and Branch History
> Injection (BHI).
You define these new TLAs here, but the code comment below does not,
making this code now impossible to understand :(
> ASM generated by compilers indicate a construct of a typical disclosure
> gadget, where an adversary-controlled register contents can be used to
> transiently access an arbitrary memory location.
If you have an "adveraray-controlled register contents", why would you
waste that on a mere speculation attack and not do something better,
like get root instead?
> Although there are no known ways to exploit this, but to be on safer
> side mitigate it by adding a speculation barrier.
>
> Reported-by: Scott D. Constable <scott.d.constable@intel.com>
> Signed-off-by: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
> ---
> net/mac80211/rc80211_minstrel_ht.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/net/mac80211/rc80211_minstrel_ht.c b/net/mac80211/rc80211_minstrel_ht.c
> index 3d91b98db099..7cf90666a865 100644
> --- a/net/mac80211/rc80211_minstrel_ht.c
> +++ b/net/mac80211/rc80211_minstrel_ht.c
> @@ -11,6 +11,7 @@
> #include <linux/moduleparam.h>
> #include <linux/ieee80211.h>
> #include <linux/minmax.h>
> +#include <linux/nospec.h>
> #include <net/mac80211.h>
> #include "rate.h"
> #include "sta_info.h"
> @@ -1999,6 +2000,14 @@ static u32 minstrel_ht_get_expected_throughput(void *priv_sta)
> struct minstrel_ht_sta *mi = priv_sta;
> int i, j, prob, tp_avg;
>
> + /*
> + * Protect against IMBTI/BHI.
This makes no sense here, right?
And you are NOT following the proper networking comment style, didn't
checkpatch complain about this?
> + *
> + * Transiently executing this function with an adversary controlled
> + * argument may disclose secrets. Speculation barrier prevents that.
> + */
> + barrier_nospec();
So how much did you just slow down the normal use of the system?
> +
> i = MI_RATE_GROUP(mi->max_tp_rate[0]);
> j = MI_RATE_IDX(mi->max_tp_rate[0]);
These are all internal structures, can't you just bounds-prevent the
speculation instead of the hard barrier?
thanks,
greg k-h
next prev parent reply other threads:[~2022-10-25 7:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 22:57 [RFC PATCH 0/2] Branch Target Injection (BTI) gadget in minstrel Pawan Gupta
2022-10-24 22:57 ` [RFC PATCH 1/2] nospec: Add a generic barrier_nospec() Pawan Gupta
2022-10-24 22:57 ` [RFC PATCH 2/2] minstrel_ht: Mitigate BTI gadget minstrel_ht_get_expected_throughput() Pawan Gupta
2022-10-25 7:36 ` Greg KH [this message]
2022-10-25 16:55 ` Pawan Gupta
2022-10-25 11:07 ` [RFC PATCH 0/2] Branch Target Injection (BTI) gadget in minstrel Peter Zijlstra
2022-10-25 19:38 ` Pawan Gupta
2022-10-25 19:56 ` Johannes Berg
2022-10-26 0:17 ` Pawan Gupta
2022-10-25 20:31 ` Peter Zijlstra
2022-10-25 22:00 ` Dave Hansen
2022-10-26 7:31 ` Peter Zijlstra
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=Y1eSGK5vylNmBbVp@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=antonio.gomez.iglesias@linux.intel.com \
--cc=daniel.sneddon@linux.intel.com \
--cc=dave.hansen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=scott.d.constable@intel.com \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).