From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-10.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_PASS,URIBL_BLOCKED,USER_AGENT_GIT autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 16CF1C43387 for ; Mon, 7 Jan 2019 13:07:00 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id D23A92089F for ; Mon, 7 Jan 2019 13:06:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1546866419; bh=9X/rLfCyixiqH6WvmjKEVmbXFKE8KPR9zuDdJLul9oM=; h=From:To:Cc:Subject:Date:In-Reply-To:References:List-ID:From; b=1wl28EcNrgCN+yeY5jGCND+Reu2fFeHspA62X6DU6MyHQ652h+yimcvWBksVHUjFz oKsz2ZjMRPQsbpIQM4T7G/e1wk0Iog/DcbySps0SRjuz2ikZnMwLIjWWvZnt9HszHf 6h0OH60TVkilwLtlmdRYcpXhoBNSYu4FsoMtJUMY= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731238AbfAGNGx (ORCPT ); Mon, 7 Jan 2019 08:06:53 -0500 Received: from mail.kernel.org ([198.145.29.99]:54152 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731236AbfAGNGx (ORCPT ); Mon, 7 Jan 2019 08:06:53 -0500 Received: from localhost (5356596B.cm-6-7b.dynamic.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 3314F217D4; Mon, 7 Jan 2019 13:06:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1546866412; bh=9X/rLfCyixiqH6WvmjKEVmbXFKE8KPR9zuDdJLul9oM=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=f4cmjqCyYta2R0cVwk/uUdaCNIO5m71h2hwb9bccHV6Ir0Z/6jTmE8lJ6ewwayqPW NCKtbLcxzW6tINSKWZ4PSClLr9FH4GkOy61p4bWTXdpVmk1a0CSiUN03m2elqS1y0T o0oJ5whFPV+QOQvKyv4hsxBIp9NqfqTTYW7KCjAs= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, "Gustavo A. R. Silva" , Takashi Iwai Subject: [PATCH 4.9 32/71] ALSA: pcm: Fix potential Spectre v1 vulnerability Date: Mon, 7 Jan 2019 13:33:01 +0100 Message-Id: <20190107105334.589888706@linuxfoundation.org> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20190107105330.280153213@linuxfoundation.org> References: <20190107105330.280153213@linuxfoundation.org> User-Agent: quilt/0.65 X-stable: review X-Patchwork-Hint: ignore MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: stable-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org 4.9-stable review patch. If anyone has any objections, please let me know. ------------------ From: Gustavo A. R. Silva commit 94ffb030b6d31ec840bb811be455dd2e26a4f43e upstream. stream is indirectly controlled by user-space, hence leading to a potential exploitation of the Spectre variant 1 vulnerability. This issue was detected with the help of Smatch: sound/core/pcm.c:140 snd_pcm_control_ioctl() warn: potential spectre issue 'pcm->streams' [r] (local cap) Fix this by sanitizing stream before using it to index pcm->streams Notice that given that speculation windows are large, the policy is to kill the speculation on the first load and not worry if it can be completed with a dependent load/store [1]. [1] https://marc.info/?l=linux-kernel&m=152449131114778&w=2 Signed-off-by: Gustavo A. R. Silva Cc: stable@vger.kernel.org Signed-off-by: Takashi Iwai Signed-off-by: Greg Kroah-Hartman --- sound/core/pcm.c | 2 ++ 1 file changed, 2 insertions(+) --- a/sound/core/pcm.c +++ b/sound/core/pcm.c @@ -25,6 +25,7 @@ #include #include #include +#include #include #include #include @@ -125,6 +126,7 @@ static int snd_pcm_control_ioctl(struct return -EFAULT; if (stream < 0 || stream > 1) return -EINVAL; + stream = array_index_nospec(stream, 2); if (get_user(subdevice, &info->subdevice)) return -EFAULT; mutex_lock(®ister_mutex);