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 1E5B11DC753 for ; Mon, 21 Oct 2024 20:11:42 +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=1729541502; cv=none; b=ZolRiLN2kAvAUiYUNfCEdCobxVfEoZUMT/wJ6p6AOU2Zbe0+P1uR6ImPEQSse1fJAKb/GoVHw2TuPuoQWkMfElrBTe3U6C3f3uA1eAhvaryLd/TzWX4XUdHWSAt/M0ky+vyY374QA8e41FqYaZMrqvsMyGf5bOQZCNDNKMsE47A= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1729541502; c=relaxed/simple; bh=LAb3GYgKwSuJbuyrm3buoDDEeIGYyQ3QhsKALvufjKQ=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=YyZqYvS3FVvGKDIO1cl2UgGL+FU5ytVEZvCM0SSqT6foG6EDkYJslVCSGHib3ONRKM+nOiC/wKn5b8L636RU54HyS3FlEX5M2EjW85OGH5eZqKf824BfUIWwr5UDRPirtqbKozYjPecySmLVUaTEgL8RPUCp3opV3dYHX1QZD/0= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=bUO9MpH2; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="bUO9MpH2" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 98830C4CEC7; Mon, 21 Oct 2024 20:11:41 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1729541502; bh=LAb3GYgKwSuJbuyrm3buoDDEeIGYyQ3QhsKALvufjKQ=; h=From:To:Cc:Subject:Date:Reply-to:From; b=bUO9MpH2Pnlqwwy/maV5oVb2eGKKBM5Pu29AnqjubJbqjFKzygiXidRYFNcVmLhZ+ EB+ylUjEfW2AxuWo/8xxHsqFoLALnA9sa0ApMEeoDEVVPp0qadarQfnVZHP2msoJdz Mv8umQG0dqWK/cYY5UKLnX+lV2Z29UNvciT8tGn4= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2022-48950: perf: Fix perf_pending_task() UaF Date: Mon, 21 Oct 2024 22:05:42 +0200 Message-ID: <2024102141-CVE-2022-48950-dc5f@gregkh> X-Mailer: git-send-email 2.47.0 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=2477; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=LAb3GYgKwSuJbuyrm3buoDDEeIGYyQ3QhsKALvufjKQ=; b=owGbwMvMwCRo6H6F97bub03G02pJDOliW0TPRwuaC51on7hChC2Y/dGrq2subHMwqu9e6aPdl Sx36+CijlgWBkEmBlkxRZYv23iO7q84pOhlaHsaZg4rE8gQBi5OAZjILkeG+Xk9qVedNVa0fH70 ZE795B+9BfU23gxzRRtET+nl7p+y+sG0slvxnP+EViltBgA= X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit Description =========== In the Linux kernel, the following vulnerability has been resolved: perf: Fix perf_pending_task() UaF Per syzbot it is possible for perf_pending_task() to run after the event is free()'d. There are two related but distinct cases: - the task_work was already queued before destroying the event; - destroying the event itself queues the task_work. The first cannot be solved using task_work_cancel() since perf_release() itself might be called from a task_work (____fput), which means the current->task_works list is already empty and task_work_cancel() won't be able to find the perf_pending_task() entry. The simplest alternative is extending the perf_event lifetime to cover the task_work. The second is just silly, queueing a task_work while you know the event is going away makes no sense and is easily avoided by re-arranging how the event is marked STATE_DEAD and ensuring it goes through STATE_OFF on the way down. The Linux kernel CVE team has assigned CVE-2022-48950 to this issue. Affected and fixed versions =========================== Fixed in 5.15.84 with commit 8bffa95ac19f Fixed in 6.0.14 with commit 78e1317a174e Fixed in 6.1 with commit 517e6a301f34 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-2022-48950 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: kernel/events/core.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/8bffa95ac19ff27c8261904f89d36c7fcf215d59 https://git.kernel.org/stable/c/78e1317a174edbfd1182599bf76c092a2877672c https://git.kernel.org/stable/c/517e6a301f34613bff24a8e35b5455884f2d83d8