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=1793635474; b=FYneumYQZYGO3oqAm7xJKLxpAlRQA2QXTmsQLJHBGtZQPEHWLyWEgSiTELg3MN1M90vZ 4M0aj5wShabyAxlqXR+uSsGNmpZAnvmDFyWoLl4C4NzY1Gr5DJSKsrT4e1z34N3cb7Gg0 2TzoUcEvbduQxm91THdq2nCl6hyNjNssaz9fE+kY56ajLPV8WDjn4O81Ly2TVHD8Afvb3 5gZTZ2grkF1xNuuB7OgTpcQaasPfSze0jtCYe6x9AGM94DNKvcGPSyOvXbhef5P6DehXP POLqSHoxFmbsfKmr1PfxMLHJn6STMwysT6vCKeOj2JNFEP6osAGLyFppPartAOJcJGQ== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1793635474; 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=YVYj4XrrGqXLeIYjA+bPfE8t5mcw6xQSMc8ngxLew34=; b=aoXp35qa/ZdBspf06znxr34FZTMKdzQKrINBNiLaCFTmMYtOPaCYqJDKtUfMno0HseGj pCadSD4x7bKyO+QSCJE3xuMVQW4vzniWvyTq4DrqCgtSgILF50o2nXu8Sr8BUA1T/YXqg kqEFI4Q155n79Nar/WtJSlSceOKhR8Zl6reh0KRIILMOjFaxsuuRwAhQLdevSzo/9kuD5 Cd/hPgAB6mXV/eXUQbeo3UrqCopMf7oRiklcS7ewU8o8W782L3mX1TXNWDeELubYFVsHq Hw8wBLxDzCTz4GpSX5Lt5sm1T/fucGNI68eMc82zE8o7BrmKu+U5B86WH896kFDWZYg== 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=DN9tWiBp; 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 9DA54606C57A for ; Mon, 2 Nov 2026 16:04:34 +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=DN9tWiBp Received: by smtp.kernel.org (Postfix) with ESMTPSA id 068C51F00A16; Mon, 2 Nov 2026 16:04:33 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1793635474; bh=YVYj4XrrGqXLeIYjA+bPfE8t5mcw6xQSMc8ngxLew34=; h=From:To:Cc:Subject:Date:Reply-To; b=DN9tWiBpPr2tHpVfI3oWL3yz2diNUwIomr2A/ctMB2SOzrD2/q1794vguHuHiu3oe 0WmWxi2Gf8WnCdg+W7GkENi6qI4PXMnh+bt2VDz5OE4O1gpdVMeeqr0msYUIV2K2KT fvIJXzkeK1gjoC0W2dzLLRQij2K+VFSyyZoBGw0o= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99237: tracing: Hold trace_types_lock when resetting last boot data from readers Date: Mon, 2 Nov 2026 17:04:20 +0100 Message-ID: <2026110206-CVE-2026-99237-24fc@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=2590; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=kCfennIbYRe5E6yQUmJKZE+91izkc5g5Qii+Mw6gLQs=; b=owGbwMvMwCRo6H6F97bub03G02pJDFkvtpRdn5D8ID7syEzxLNfM7PaJb54n24r+CFhtl/kuO 5599o5vHbEsDIJMDLJiiixftvEc3V9xSNHL0PY0zBxWJpAhDFycAjAR59sM832bp82cqRnjvaOz RfXh+sn3D7HnfmdYsNlc9vHrC+lZr/XO1Id1nhKcxzNvMQA= 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: tracing: Hold trace_types_lock when resetting last boot data from readers update_last_data_if_empty() is called from tracing_open() with O_TRUNC, tracing_read_pipe() and tracing_buffers_read() without trace_types_lock. Two readers can both pass the LAST_BOOT test and free module_delta twice, and a module notifier can update module_delta while it is being freed. Take trace_types_lock in those paths and keep the callers that already hold it on an unlocked variant. The Linux kernel CVE team has assigned CVE-2026-99237 to this issue. Severity ======== CVSS v3.1: 7.8 HIGH Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Affected and fixed versions =========================== Issue introduced in 6.16 with commit 32dc0042528d385d83bf458e4cf3a49c5110afea and fixed in 6.18.60 with commit 92b69f6db640dadc0851762ee2e12db99f083cad Issue introduced in 6.16 with commit 32dc0042528d385d83bf458e4cf3a49c5110afea and fixed in 7.2.14 with commit d6d991afe775ab7fcf89523a2502b7ca3be56ffd Issue introduced in 6.16 with commit 32dc0042528d385d83bf458e4cf3a49c5110afea and fixed in 7.3.1 with commit 1f06cfe0b60a878619d1d8efe1cd0f515b7dc2aa 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-99237 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/trace/trace.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/92b69f6db640dadc0851762ee2e12db99f083cad https://git.kernel.org/stable/c/d6d991afe775ab7fcf89523a2502b7ca3be56ffd https://git.kernel.org/stable/c/1f06cfe0b60a878619d1d8efe1cd0f515b7dc2aa https://git.kernel.org/stable/c/5a6bd62f09147b49b31fd19d4eba122cb5f941a1