From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id EAF59367F3A for ; Sat, 15 Aug 2026 06:19:15 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786774757; cv=none; b=OGo7yyz7nb7HN6LaoOixChH6z4dT1ch1sEhghlm2lvxd7nePov4+ITEXLoDlEzZuKrBnhwt0HterCHmz18h8aZzhCTHBawB3PoYNavJG+EJQlrg1DoRnT2z7Svpzo5M1J6icD75BYki8tzTmV40xQYzTx+gOFrjpYdRqMpIAumw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786774757; c=relaxed/simple; bh=4I1mvni/+KbwPZ0vwBcNBrCrEm58M5Yo5w2bMr0rCUM=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=jKA6gA+ErHFnp/8o0VXgC9eaCHJEFwLoiF5Fnn52eva5/m2MefUQs8cIXlNudYMxntJQtUtjgO9Eq/GsMG5ycba6iJXWIqY0dTlCssLrQGy+xJYkG3dTpkzYLp5W447g7jClC32w0s684x+bd/YFnXoccC+5oCV68Q9JdcEhgKI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=O9Wcp0Pu; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="O9Wcp0Pu" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 4D7931F000E9; Sat, 15 Aug 2026 06:19:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1786774755; bh=aJCyhowkJGN5B9H2DwVNbiLcDDVS6LOtnRf62L1l5fg=; h=From:To:Cc:Subject:Date:Reply-To; b=O9Wcp0Pu7LHWZYeC4dtEfDfj3BpNIsccqeexIWkbBq1tkJM/U9uqNlk/UIPLymY25 l32cGqV68/KRCnCfOwGANnS58MS5v32kdiN2Oy9/LTIiNMkSNRF9KhlWIUFkwU4R39 wJCcPrkYXnKw0LawUXoccwFw5vt9YZu99gYrqeis= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-72262: ASoC: SOF: ipc3-control: Fix heap overflow in bytes_ext put/get Date: Sat, 15 Aug 2026 15:05:41 +0900 Message-ID: <2026081555-CVE-2026-72262-c47f@gregkh> X-Mailer: git-send-email 2.55.0 Reply-To: , Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=3351; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=JFwy10Il7sA1HAFp3u0ESNd4JdFEDQMUL3fUS4BdmRY=; b=owGbwMvMwCRo6H6F97bub03G02pJDFkNDJeb/nxl6A+e9mnaquTvWv9afCxm+t0yXrmP/4Ffw 19+gabMjlgWBkEmBlkxRZYv23iO7q84pOhlaHsaZg4rE8gQBi5OAZiIOjvDbBYHli09YQJPGJg6 eEwfX0tL31KygmF+zcIzP/iTL/VeyJ1ZZhSumcNXGncXAA== X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman Description =========== In the Linux kernel, the following vulnerability has been resolved: ASoC: SOF: ipc3-control: Fix heap overflow in bytes_ext put/get The ipc_control_data buffer is allocated as kzalloc(max_size), where max_size covers the entire struct sof_ipc_ctrl_data including its flexible array payload. However, the bounds checks in bytes_ext_put and _bytes_ext_get compared user data lengths against max_size directly, ignoring that cdata->data sits at an offset of sizeof(struct sof_ipc_ctrl_data) bytes into the allocation. This allowed writing up to sizeof(struct sof_ipc_ctrl_data) bytes past the end of the heap buffer from unprivileged userspace via the ALSA TLV kcontrol interface, and similarly allowed over-reading adjacent heap data on the get path. Fix all bounds checks to subtract sizeof(*cdata) from max_size so they reflect the actual space available at the cdata->data offset. Also fix the error-path restore in bytes_ext_put which wrote to cdata->data instead of cdata, causing the same overflow. The Linux kernel CVE team has assigned CVE-2026-72262 to this issue. Affected and fixed versions =========================== Issue introduced in 5.18 with commit 67ec2a091630c28ea8d05db2bd7178a05b04b7e6 and fixed in 6.6.145 with commit 1adde1941bba7b0d7104b86ed819d48d81cb0ad9 Issue introduced in 5.18 with commit 67ec2a091630c28ea8d05db2bd7178a05b04b7e6 and fixed in 6.12.97 with commit eaa67e139c9217099e2a7b717aeeb46c65de3494 Issue introduced in 5.18 with commit 67ec2a091630c28ea8d05db2bd7178a05b04b7e6 and fixed in 6.18.40 with commit 121577383b5cf221e86581e0f2bcca4c66f17469 Issue introduced in 5.18 with commit 67ec2a091630c28ea8d05db2bd7178a05b04b7e6 and fixed in 7.1.5 with commit f4933e1d11b97b6a0951648b7c3e53850e1b33a9 Issue introduced in 5.18 with commit 67ec2a091630c28ea8d05db2bd7178a05b04b7e6 and fixed in 7.2-rc1 with commit fd46668d538993218eea19c6925c868ac0f2630c Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2026-72262 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: sound/soc/sof/ipc3-control.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: https://git.kernel.org/stable/c/1adde1941bba7b0d7104b86ed819d48d81cb0ad9 https://git.kernel.org/stable/c/eaa67e139c9217099e2a7b717aeeb46c65de3494 https://git.kernel.org/stable/c/121577383b5cf221e86581e0f2bcca4c66f17469 https://git.kernel.org/stable/c/f4933e1d11b97b6a0951648b7c3e53850e1b33a9 https://git.kernel.org/stable/c/fd46668d538993218eea19c6925c868ac0f2630c