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 555C23CC7F8 for ; Fri, 28 Aug 2026 06:52:43 +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=1787899965; cv=none; b=pqdaYQ6ITxmaELeP/voofbM4K7uMvxRAYUHlql7DWg97PiKg1brSEMDOCF0HgOAOHiMXe/eNop1D5Q2F1XPIBSJnevLCDiNtY4jns8RLVlLNwjsjNqZMf6RdlScgwNQYsz1s8CVLeFtf356vmFfA5Fam02oN+nNOzd6YsYMuMGI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1787899965; c=relaxed/simple; bh=TOy7wGiPH2cNnOaggHUOjycUgl115A/uURIraeyLboQ=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=gncYQZKtkMr9ATi2/0CaDYUl2E8buQpbZWWfb+r6Ae/HlCuvwmscnfaMENk13UiwzOnIqA7TZ4TNneN58QsxexKGCkkSO7ci/Ij/gwanA1GszuZN/m4wimrJe7f5d+vngwg5JJ5365MRV2Ci9zZ317kNB9Et3u96fQH7MEXSAaE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=v/nDO0Ot; 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="v/nDO0Ot" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 62FF91F000E9; Fri, 28 Aug 2026 06:52:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1787899962; bh=JjSUGZwvbPWfP0ooNh3gnRkhrqDRWQ0tUQiUl6+xwB0=; h=From:To:Cc:Subject:Date:Reply-To; b=v/nDO0Ot8CD6+35S/+NTRKowDSkh798PbmXrOZ1NtmPnv3Hz6kw+PNytjhW+bhvJf pmYHJTyULbCluJqkcC/QJcincx1AitphiXqbN77HH6sftF4vOP1rDR+jK5CT60gTWt prPxnxH+8XTjM8jWB/zBABTHjuG831+QMYuC0CtM= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-80671: perf sched: Fix register_pid() overflow, strcpy, and BUG_ON Date: Fri, 28 Aug 2026 08:49:48 +0200 Message-ID: <2026082848-CVE-2026-80671-e54e@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=3075; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=Cz85WisKUsVtGBezBeYJVAin/dhOJ/zjNT53hxCjnXY=; b=owGbwMvMwCRo6H6F97bub03G02pJDFkT9QOeT0q/fzz16PQLAc8jTpkWvlv9/mZZybVZ9cf7l Q89sBOf3RHLwiDIxCArpsjyZRvP0f0VhxS9DG1Pw8xhZQIZwsDFKQATOenAML9k6r4X2+oen3lm 4h1c9nSyxOunTlkMs9l/Zz4InsFs+elgStT12l3MM2Y8yAIA 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: perf sched: Fix register_pid() overflow, strcpy, and BUG_ON register_pid() has several issues when processing untrusted perf.data: 1. Integer overflow: (pid + 1) * sizeof(struct task_desc *) can wrap to a small value on 32-bit systems when pid is large (e.g. 0x40000000), causing realloc to return a tiny buffer followed by out-of-bounds writes in the initialization loop. 2. Heap buffer overflow: strcpy(task->comm, comm) copies the untrusted comm string into a fixed 20-byte COMM_LEN buffer with no length check. 3. BUG_ON on allocation failure: perf.data is untrusted input, so allocation failures should be handled gracefully rather than killing the process. 4. Realloc of sched->tasks assigned directly back, leaking the old pointer on failure; nr_tasks incremented before the realloc, leaving corrupted state on failure. Cap pid at PID_MAX_LIMIT (4194304, matching the kernel's maximum on 64-bit), replace strcpy with strlcpy, guard against NULL comm, replace BUG_ON with NULL returns using safe realloc patterns, and add NULL checks in callers that dereference the result. The Linux kernel CVE team has assigned CVE-2026-80671 to this issue. Affected and fixed versions =========================== Issue introduced in 2.6.32 with commit ec156764d424dd67283c2cd5e9f6f1b8388364ac and fixed in 6.18.40 with commit 652cea73b7b7b7c622a2be670e44e3c499c6d49f Issue introduced in 2.6.32 with commit ec156764d424dd67283c2cd5e9f6f1b8388364ac and fixed in 7.1.5 with commit 5ea1dcc9418c4e06ce29ed5170596f497ba86872 Issue introduced in 2.6.32 with commit ec156764d424dd67283c2cd5e9f6f1b8388364ac and fixed in 7.2 with commit 5949d339f5ec98752d56dcd4e36f619a59d513a5 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-80671 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: tools/perf/builtin-sched.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/652cea73b7b7b7c622a2be670e44e3c499c6d49f https://git.kernel.org/stable/c/5ea1dcc9418c4e06ce29ed5170596f497ba86872 https://git.kernel.org/stable/c/5949d339f5ec98752d56dcd4e36f619a59d513a5