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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 26098C433F5 for ; Fri, 15 Apr 2022 16:01:33 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1355586AbiDOQD7 (ORCPT ); Fri, 15 Apr 2022 12:03:59 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42628 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1349398AbiDOQDx (ORCPT ); Fri, 15 Apr 2022 12:03:53 -0400 Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 23C849D0EE for ; Fri, 15 Apr 2022 09:01:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1650038485; x=1681574485; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=iU32Nth3Vpx4ScnrV9cfqu6DrMgNq7G4TYDO0DOA9XI=; b=KZnsSvRpfb5gk3x/5zE2OHpZNd1h+7uRn2GErb46ZItFYC2qD70xuLWw C5YM+GMl4eJ+dDdUNgJMu07Ug3G+0X/QopJ28Y08DcP3u2iYM2xLmh7Sw 3qXDgpactPrFaWMXDNqqR8kpaomHFCUVCKmDgpjLx3HsFan1W/m0xgyXd vusNkjEGBkFuxWKjF/9MEMjTIm7j519EqJBD41sGQestsC4nY8ryesLm8 YnnIi1gA3t3c0binQO3uyvki8Tzqvhgm3xJ8c9MJ0oVQBOHKMrVjsYQWi PiCsiHmLFaUOrAZG8wtFe6k8jOh75HVO++RF27ec0t02qgRj3yzUQejo2 Q==; X-IronPort-AV: E=McAfee;i="6400,9594,10318"; a="288238669" X-IronPort-AV: E=Sophos;i="5.90,263,1643702400"; d="scan'208";a="288238669" Received: from orsmga007.jf.intel.com ([10.7.209.58]) by fmsmga101.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 15 Apr 2022 09:00:59 -0700 X-IronPort-AV: E=Sophos;i="5.90,263,1643702400"; d="scan'208";a="553197301" Received: from gkcarda-mobl2.amr.corp.intel.com (HELO [10.251.1.179]) ([10.251.1.179]) by orsmga007-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 15 Apr 2022 09:00:57 -0700 Message-ID: <8eeb08ec-4836-cf7d-2285-8ed74ccfc1cb@linux.intel.com> Date: Fri, 15 Apr 2022 11:00:48 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Firefox/91.0 Thunderbird/91.5.0 Subject: Re: out-of-bounds access in sound/soc/sof/topology.c Content-Language: en-US To: Sergey Senozhatsky , Liam Girdwood , Ranjani Sridharan , Kai Vehmanen , Jaska Uimonen , =?UTF-8?Q?P=c3=a9ter_Ujfalusi?= Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org, Takashi Iwai , Tomasz Figa , Mark Brown , Ricardo Ribalda , sound-open-firmware@alsa-project.org References: From: Pierre-Louis Bossart In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Thanks Sergey for this email. On 4/15/22 04:23, Sergey Senozhatsky wrote: > Hi, > > I'm running 5.10.111 LTS, so if this has been fixed already then we definitely > want to cherry pick the fix for -stable. > > > Anonymous union in this struct is of zero size > > /* generic control data */ > struct sof_ipc_ctrl_data { > struct sof_ipc_reply rhdr; > uint32_t comp_id; > > /* control access and data type */ > uint32_t type; /**< enum sof_ipc_ctrl_type */ > uint32_t cmd; /**< enum sof_ipc_ctrl_cmd */ > uint32_t index; /**< control index for comps > 1 control */ > > /* control data - can either be appended or DMAed from host */ > struct sof_ipc_host_buffer buffer; > uint32_t num_elems; /**< in array elems or bytes for data type */ > uint32_t elems_remaining; /**< elems remaining if sent in parts */ > > uint32_t msg_index; /**< for large messages sent in parts */ > > /* reserved for future use */ > uint32_t reserved[6]; > > /* control data - add new types if needed */ > union { > /* channel values can be used by volume type controls */ > struct sof_ipc_ctrl_value_chan chanv[0]; > /* component values used by routing controls like mux, mixer */ > struct sof_ipc_ctrl_value_comp compv[0]; > /* data can be used by binary controls */ > struct sof_abi_hdr data[0]; > }; > } __packed; > > sof_ipc_ctrl_value_chan and sof_ipc_ctrl_value_comp are of the same > size - 8 bytes, while sof_abi_hdr is much larger - _at least_ 32 bytes > (`__u32 data[0]` in sof_abi_hdr suggest that there should be more > payload after header). But they all contribute 0 to sizeof(sof_ipc_ctrl_data). > > Now control data allocations looks as follows > > scontrol->size = struct_size(scontrol->control_data, chanv, > le32_to_cpu(mc->num_channels)); > scontrol->control_data = kzalloc(scontrol->size, GFP_KERNEL); > > Which is sizeof(sof_ipc_ctrl_data) + mc->num_channels * sizeof(sof_ipc_ctrl_value_chan) > > For some reason it uses sizeof(sof_ipc_ctrl_value_chan), which is not > the largest member of the union. > > And this is where the problem is: in order to make control->data.FOO loads > and stores legal we need mc->num_channels to be of at least 4. So that > > sizeof(sof_ipc_ctrl_data) + mc->num_channels * sizeof(sof_ipc_ctrl_value_chan) > > 92 + 4 * 8 > > will be the same as > > sizeof(sof_ipc_ctrl_data) + sizeof(sof_abi_hdr). > > 92 + 32 > > Otherwise scontrol->control_data->data.FOO will access nearby/foreign > slab object. > > And there is at least one such memory access. In sof_get_control_data(). > > wdata[i].pdata = wdata[i].control->control_data->data; > *size += wdata[i].pdata->size; > > pdata->size is at offset 8, but if, say, mc->num_channels == 1 then > we allocate only 8 bytes for pdata, so pdata->size is 4 bytes outside > of allocated slab object. > > Thoughts? The SOF contributors who wrote that code are all on an extended Easter week-end or vacation so we'll need more time to provide a definitive answer. I am far from an expert on the topology, but I note that the 'data' field is only used for binary controls, where we use the maximum possible size for a control, without any arithmetic involving channels. It makes sense to me, the binary data does not have any defined structure, it's just a bunch of bytes provided as is to the firmware. static int sof_ipc3_control_load_bytes(struct snd_sof_dev *sdev, struct snd_sof_control *scontrol) { struct sof_ipc_ctrl_data *cdata; int ret; scontrol->ipc_control_data = kzalloc(scontrol->max_size, GFP_KERNEL); if (!scontrol->ipc_control_data) return -ENOMEM; In other cases, such as volumes and enums, the 'data' field doesn't seem to be used but we do use the channel information for volume and enums. static int sof_ipc3_control_load_volume(struct snd_sof_dev *sdev, struct snd_sof_control *scontrol) { struct sof_ipc_ctrl_data *cdata; int i; /* init the volume get/put data */ scontrol->size = struct_size(cdata, chanv, scontrol->num_channels); scontrol->ipc_control_data = kzalloc(scontrol->size, GFP_KERNEL); static int sof_ipc3_control_load_enum(struct snd_sof_dev *sdev, struct snd_sof_control *scontrol) { struct sof_ipc_ctrl_data *cdata; /* init the enum get/put data */ scontrol->size = struct_size(cdata, chanv, scontrol->num_channels); scontrol->ipc_control_data = kzalloc(scontrol->size, GFP_KERNEL); if (!scontrol->ipc_control_data) Given that we have two ways of allocating the memory, I am not sure there is a problem, but I could be wrong. I checked the v5.10.111 code and I see the same code, with the max_size being used for sof_control_load_bytes() and no channel-based arithmetic. Can I ask how you found out about this problem, is this the result of a warning/error reported by a software tool or based on your reviews of the code? Thanks -Pierre