From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 6F3A216064E for ; Thu, 29 Feb 2024 15:53:40 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1709222020; cv=none; b=RPFJ0VpwXeACeoB3mqNOJBacB+jKjt92NHjbdnhM2kCsd7bXDdaSRECAgJiM13N4iFyOJB5GqeEvXFBqGKX51BBOiuLwW6joNRPJZ6gnhO+HIYjx2r205fZX1sAk6o4Jm3m7oOX1vzquRNL3RN7RaTsWIg1gXpCVsh1qABCy3ZQ= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1709222020; c=relaxed/simple; bh=+Fg6Kg5MC6YqOF8zgxTAlNQt3vaALYVhaAe99dpPUvc=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=ia+UwWuCrmP81GXobFSI268Lou20/vh5s79YppJn4SQIkulQgCo3PkxUYDBfF6BG7CTOWqPNq/1hJrZFdYU/Umw6/LXcX5obkpdyBIMefJmRv39jnKTFtMmCDqDBSRTIP1EjZpANt3rExYVwdwX2zSmry9qDsCC59LmD5F1eFKo= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=WlfIEIpy; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="WlfIEIpy" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 4E6AFC433C7; Thu, 29 Feb 2024 15:53:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1709222020; bh=+Fg6Kg5MC6YqOF8zgxTAlNQt3vaALYVhaAe99dpPUvc=; h=From:To:Cc:Subject:Date:Reply-to:From; b=WlfIEIpySLPIHOAOo7XJtoiDrXwzTFOA4roOqgSQ2i2GnsvxrdlWmNfOo/qwahRQI TC/tKKb6cu20pXtrr7LE/pQdQbQBg7QMEEyOUMz6C963bj+3GRkJM118HzNTI3KwfU Wlr2MW6iQe2ccMlQgVx6Pll3ferGB2QMvjV4VfV7sZjeLl3Qx6b+uLlMG+Xh4ciRSn I8d4yOjchLO1my4G6/k6ZIbFrykJr4zNGODksDc7CBNfDwAdyO2a4ZC+weS5rX+/MH 7VUuVbAjYXiNl9V738Eg3EUkNBUtQWWDVoQFm7LF87EAmRJktzqLktAADiUDuPS3Qc 66Q3lNDOs8Cag== From: Lee Jones To: linux-cve-announce@vger.kernel.org Cc: Lee Jones Subject: CVE-2024-26618: arm64/sme: Always exit sme_alloc() early with existing storage Date: Thu, 29 Feb 2024 15:53:09 +0000 Message-ID: <20240229155245.1571576-50-lee@kernel.org> X-Mailer: git-send-email 2.44.0.rc1.240.g4c46232300-goog Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Reply-to: , X-Developer-Signature: v=1; a=openpgp-sha256; l=2195; i=lee@kernel.org; h=from:subject; bh=+Fg6Kg5MC6YqOF8zgxTAlNQt3vaALYVhaAe99dpPUvc=; b=owEBbQKS/ZANAwAKAVGvii+H/HdhAcsmYgBl4KhQeCD/t/QEuuREvDAo9CfCV231YxO882CWe cLkBvSldpqJAjMEAAEKAB0WIQR2tsk1o74gmpTwh0hRr4ovh/x3YQUCZeCoUAAKCRBRr4ovh/x3 Yan8D/4raWb609zI+mpfMX3UsWbT8a6Y1yRUn68D/1z2cr+AdXhV4RXzBViIbPcFzPIA/QPv6oR ioEmnsWRjWNYJeOWFHlWy+6vt9mhSAdPtHDbLgyWLCTzIXUezKAVrbnENjXe/YsXVKpwuhk+726 9LLRc27s2wifNs9Fwc/YKY1+mnSsOW3CEyev8+SjvnQWbQGZBfPfVsTuDtRWZfVSJ5kTmOqNcAd CGk2Y7/qBqAp7DNT2ZjBfl8i+zZOErN2kxvcaiUkAhxOv3/l76RXUiqbidbBUfdQJDjqalXQMN3 Sru8hXF57O6t7bXIO1Qq0eqTEUDgpbhBRyD8GySF8C1pFtw/nSpcXd2seF9lG5e5p1kRT2Ps7L4 Vep8LVT0VAoLOT0B4CMadYNFEanVGpdViIuwqb4WmHZQ/Ar8vlWRTjp47Mx5HgX6jhphVd+K640 TmCpKHZhJmLNnRKEvQwxMhrGYXwdZRFD4/3gA/Pdxh3QBZrVq1MKjU1heEhiK8arEK6nx0a61/Z LWd4WBxZOsNkcPy39n5sS8RpqJNFB0WJnJ0XSTpes81fcaVcLZVJOSrg5KH9TL/nj25iX8AfPPM NxUxaNam0XfGLH/0L8hDYGP7G1KcmloFke/4EFMZ3CY3D1Fbrodrmp5DWCtC6reQA/E9PTn5FR5 5y7aiLwk5HVmovw== X-Developer-Key: i=lee@kernel.org; a=openpgp; fpr=76B6C935A3BE209A94F0874851AF8A2F87FC7761 Content-Transfer-Encoding: 8bit Description =========== In the Linux kernel, the following vulnerability has been resolved: arm64/sme: Always exit sme_alloc() early with existing storage When sme_alloc() is called with existing storage and we are not flushing we will always allocate new storage, both leaking the existing storage and corrupting the state. Fix this by separating the checks for flushing and for existing storage as we do for SVE. Callers that reallocate (eg, due to changing the vector length) should call sme_free() themselves. The Linux kernel CVE team has assigned CVE-2024-26618 to this issue. Affected and fixed versions =========================== Issue introduced in 6.5 with commit 5d0a8d2fba50 and fixed in 6.6.15 with commit 569156e4fa34 Issue introduced in 6.5 with commit 5d0a8d2fba50 and fixed in 6.7.3 with commit 814af6b4e600 Issue introduced in 6.5 with commit 5d0a8d2fba50 and fixed in 6.8-rc1 with commit dc7eb8755797 Please see https://www.kernel.org or 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-2024-26618 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: arch/arm64/kernel/fpsimd.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/569156e4fa347237f8fa2a7e935d860109c55ac4 https://git.kernel.org/stable/c/814af6b4e6000e574e74d92197190edf07cc3680 https://git.kernel.org/stable/c/dc7eb8755797ed41a0d1b5c0c39df3c8f401b3d9