From: Takashi Iwai <tiwai@suse.de>
To: alsa-devel@alsa-project.org
Cc: Dan Carpenter <dan.carpenter@oracle.com>
Subject: [PATCH 4/8] ALSA: hda: Hardening for potential Spectre v1
Date: Tue, 24 Apr 2018 09:56:15 +0200 [thread overview]
Message-ID: <20180424075619.29602-5-tiwai@suse.de> (raw)
In-Reply-To: <20180424075619.29602-1-tiwai@suse.de>
As the recent Smatch warned, one place in HD-audio hwdep ioctl codes
may expand the array directly from the user-space value with
speculation:
sound/pci/hda/hda_local.h:467 get_wcaps() warn: potential spectre issue 'codec->wcaps'
As get_wcaps() itself is a fairly frequently called inline function,
and there is only one single call with a user-space value, it's better
to open-code it locally with array_index_nospec() hardening.
BugLink: https://marc.info/?l=linux-kernel&m=152411496503418&w=2
Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
Signed-off-by: Takashi Iwai <tiwai@suse.de>
---
sound/pci/hda/hda_hwdep.c | 12 +++++++++++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/sound/pci/hda/hda_hwdep.c b/sound/pci/hda/hda_hwdep.c
index 57df06e76968..cc009a4a3d1d 100644
--- a/sound/pci/hda/hda_hwdep.c
+++ b/sound/pci/hda/hda_hwdep.c
@@ -21,6 +21,7 @@
#include <linux/init.h>
#include <linux/slab.h>
#include <linux/compat.h>
+#include <linux/nospec.h>
#include <sound/core.h>
#include "hda_codec.h"
#include "hda_local.h"
@@ -51,7 +52,16 @@ static int get_wcap_ioctl(struct hda_codec *codec,
if (get_user(verb, &arg->verb))
return -EFAULT;
- res = get_wcaps(codec, verb >> 24);
+ /* open-code get_wcaps(verb>>24) with nospec */
+ verb >>= 24;
+ if (verb < codec->core.start_nid ||
+ verb >= codec->core.start_nid + codec->core.num_nodes) {
+ res = 0;
+ } else {
+ verb -= codec->core.start_nid;
+ verb = array_index_nospec(verb, codec->core.num_nodes);
+ res = codec->wcaps[verb];
+ }
if (put_user(res, &arg->res))
return -EFAULT;
return 0;
--
2.16.3
next prev parent reply other threads:[~2018-04-24 7:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 7:56 [PATCH 0/8] ALSA: Hardening for potential Spectre v1 Takashi Iwai
2018-04-24 7:56 ` [PATCH 1/8] ALSA: seq: oss: Fix unbalanced use lock for synth MIDI device Takashi Iwai
2018-04-24 7:56 ` [PATCH 2/8] ALSA: seq: oss: Hardening for potential Spectre v1 Takashi Iwai
2018-04-24 7:56 ` [PATCH 3/8] ALSA: control: " Takashi Iwai
2018-04-24 7:56 ` Takashi Iwai [this message]
2018-04-24 7:56 ` [PATCH 5/8] ALSA: opl3: " Takashi Iwai
2018-04-24 7:56 ` [PATCH 6/8] ALSA: asihpi: " Takashi Iwai
2018-04-24 7:56 ` [PATCH 7/8] ALSA: hdspm: " Takashi Iwai
2018-04-24 7:56 ` [PATCH 8/8] ALSA: rme9652: " Takashi Iwai
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=20180424075619.29602-5-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=dan.carpenter@oracle.com \
/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