From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=100.103.45.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1792758582; b=bv0t2SNcT9ADETj9dCQG6oAAhualahaB5BrpWYyYPDmNwc9QbaYlN53H3IyTF2nTUEiA /2UQoPVIdZL+Xyi8XKBqSRwI/lqSrJEiV71hBdzPhuigTEXZW0Ol/4MOl0KGHQRWI0kLK aZSmBEqyiTmo4yOgox7LZkenaXgDccneojXgEkzRs87/96gcrfGEiwq+29HryKXtnAho2 EuQwgSElKot+4V4dD0nlO156H1xgdjQaOmnl3K8jx2nGDLsH5mVMcgCNTUSDU3RxBk3yW IWnwpRM9lcfkf8rkMO40teM1wmRu8x3yG+CgmLtbmxbUxmpQVGEfRP4vy6NeGOWD09g== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1792758582; h=Received:DKIM-Signature:From:To:Cc:Subject:Date:Message-ID:X-Mailer: Reply-To:MIME-Version:Lines:X-Developer-Signature:X-Developer-Key: Content-Transfer-Encoding; bh=fLq5OxumVCCVV4RxYYgIcIBXm9DIiZ744Lyiej3R1uE=; b=PCcowCN5wdQWf9+ljWYkINeVI+4i0OIR9H3s7d1Qbc+l6dlAaNyW0bL69+3LLH1GJsRG 0gwb0PMteuPt9zSsmyZ1e1YJGk0+ZqY0KBCpFqpsWmpcy5AXBftiAGKo4l3c3JBUtdRNb kpl+2+Q9Vq+b0SxAioElAQ7p1UeP0tk9Hsni52le/1f0jbSqBk3DL6b4VfjuNk8+myQX0 UAIHpkKqivq2NppHdqBvq5ZL3oHC+PPeFyQ03Kp5Zfz59uzQDcZR9V+eN9zytjKvk6O3g gZQiDpCS2rjFvSy9RcBMUGu95SRDo/vTGkDmIzXXnlSZubT6NWM/8fhrKBebQ/NqFEg== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=JPv+cBzQ; arc=none smtp.remote-ip=100.103.45.18 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 76CA8606A31A for ; Fri, 23 Oct 2026 12:29:42 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key, unprotected) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=JPv+cBzQ Received: by smtp.kernel.org (Postfix) with ESMTPSA id E9A651F01825; Fri, 23 Oct 2026 12:29:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1792758582; bh=fLq5OxumVCCVV4RxYYgIcIBXm9DIiZ744Lyiej3R1uE=; h=From:To:Cc:Subject:Date:Reply-To; b=JPv+cBzQy5ekYn+jDrPcHwrZpb0MsNW0kaJGtJuf/1AQaes6P5RHdORsP+qJQG7bX og3J/zdmJuLOfZT0ST35AbNYXBKn+Euq+lbHUWGHbV1BVXlptmkudRDHeceMkdmb/H lHaxRM5bWKQRODgM/h89u0CtbTceHsBSEAR9kHW8= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-98951: riscv: ptrace: Zero-initialize regset buffers before copyin Date: Fri, 23 Oct 2026 14:19:13 +0200 Message-ID: <2026102306-CVE-2026-98951-e58c@gregkh> X-Mailer: git-send-email 2.56.0 Reply-To: , X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=2209; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=0hs4ZsV9kt9fBm9Rb9hy11Dn8BOoEp8bEuAb2vkvels=; b=owGbwMvMwCRo6H6F97bub03G02pJDFm3A3ZxnF3x4sM5Jqmi4gmr3rnsZ2PT90mXc6h+wFypG NaV8tG3I5aFQZCJQVZMkeXLNp6j+ysOKXoZ2p6GmcPKBDKEgYtTACaS78Ywm+X3or6SJafWpHnw 9hU80snbsMREgmF+kcfOQLXq/uRjzeX9itNEvj+exZsPAA== 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: riscv: ptrace: Zero-initialize regset buffers before copyin user_regset_copyin() only copies `count` bytes, so a PTRACE_SETREGSET request with a short iov_len leaves the rest of the stack buffer uninitialized. In riscv_vr_set() that garbage is validated and copied into the target's vstate, and in riscv_cfi_set() it can be stored as the target's shadow stack pointer. Zero both buffers, as the get path already does. The Linux kernel CVE team has assigned CVE-2026-98951 to this issue. Affected and fixed versions =========================== Issue introduced in 6.6 with commit 9300f00439743c4a34d735e1a27118eb68a1504e and fixed in 7.2.11 with commit 89fc70d73f4ac8781f9e15edd1dbc6b6088453b3 Issue introduced in 6.6 with commit 9300f00439743c4a34d735e1a27118eb68a1504e and fixed in 7.3 with commit 59052a88ba5fe4a7bb34b3a0a42aa5d453d3bb97 Issue introduced in 6.5.3 with commit f2a9cd050901c4734bc175294c3bd6a40a1a9e99 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-98951 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/riscv/kernel/ptrace.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/89fc70d73f4ac8781f9e15edd1dbc6b6088453b3 https://git.kernel.org/stable/c/59052a88ba5fe4a7bb34b3a0a42aa5d453d3bb97