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 4D2DF49364A for ; Fri, 25 Sep 2026 10:29: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=1790332184; cv=none; b=ptN7HCzoIUxGW4mM5VvcC1AcQktVa9AFLXHsIbJIehFyEcmVTZSj+OF/+fHgAilaIftRnXYN1gKiTKdhuTPZv1l1Z7t9q3swn2OTPWLcfkCzX5Prd3FffEValluYkVpjri0ukRl42DHleDU2j8Nq8R4/MuiOV0l7fv2uku3qWMQ= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1790332184; c=relaxed/simple; bh=UTcxJ/TuSCLj3SRPfakczALFZFhs+LQcRhxy68oQZtg=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=YvkeBhS2+YfPo7Gyz9zXtLm4oc5zJrFV6RrNcnoWQo9lyLvSl6drjuE7PDk9NB1lkmb/ndKyiLeLRzm3vG0mk+u8BXxTvuIQvxg2SkGQkONs77vN37fvJNioRKSB9p5BkmgS63/zKmeaKq8irUHSW6hEtLMt+EsinvEtEecolnI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=UAszbucU; 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="UAszbucU" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 6BED01F000FF; Fri, 25 Sep 2026 10:29:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1790332183; bh=LWTQDOleVaGaR93rlb/GlLXenIT0JHHsyObcopXAHrY=; h=From:To:Cc:Subject:Date:Reply-To; b=UAszbucULzXT3AB0CVvwiSitBXnUSiAWRd0sXcxShPOuoCBhRaSMD29Sq4zJyVbs5 ZObruJlnEDCQiIZZDxZlRnNvzOVpdGRxX2ADa/Ir9edIoqtXDd1y5modsF/m/ZDTtb 9lp1bPGXgInSG8OO0bhEG8+IBs2FVyE5BKLqXOn8= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-97617: ring-buffer: Check resize_disabled before publishing the new subbuf order Date: Fri, 25 Sep 2026 12:23:17 +0200 Message-ID: <2026092503-CVE-2026-97617-453f@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=2703; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=5G2ryi8aRAEWM98Xu+wrIYdXGs6f+cojsQbrJCssZx8=; b=owGbwMvMwCRo6H6F97bub03G02pJDFnbvL3PrnnO6v64Vdpqxu3eKafb034eOLfi9cY1a8NXz 3sns3RWZ0csC4MgE4OsmCLLl208R/dXHFL0MrQ9DTOHlQlkCAMXpwBMJOgrw4JFc7TYzWu7Lqus icpbZfU1jMEz7hvDgrMb1S10WxQ1b3fHrhUtqcx8uHfJRwA= 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: ring-buffer: Check resize_disabled before publishing the new subbuf order ring_buffer_subbuf_order_set() stores the new order and only then walks the CPUs, returning -EBUSY if any of them has resizing disabled. A user mapped buffer has resizing disabled, and __rb_map_vma() reads buffer->subbuf_order without buffer->mutex, so an mmap of an already mapped CPU racing the failing order change sizes the mapping with the new order and inserts pages past the sub-buffer into the VMA. Check the CPUs before storing the new order. The Linux kernel CVE team has assigned CVE-2026-97617 to this issue. Affected and fixed versions =========================== Issue introduced in 6.10 with commit 117c39200d9d760cbd5944bb89efb7b9c51965aa and fixed in 6.12.111 with commit f2099644e1b2a2c0805c5240d63ab0522d9d0174 Issue introduced in 6.10 with commit 117c39200d9d760cbd5944bb89efb7b9c51965aa and fixed in 6.18.53 with commit 9fd4ea952e6ac12a63c3fe89f08ad02771aa2c06 Issue introduced in 6.10 with commit 117c39200d9d760cbd5944bb89efb7b9c51965aa and fixed in 7.2.7 with commit 32bf47db9237c5b8b6f6aaa5356bb4c79d241f76 Issue introduced in 6.10 with commit 117c39200d9d760cbd5944bb89efb7b9c51965aa and fixed in 7.3-rc3 with commit d860c67c051685abb0460b593b193f0f45f4fa92 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-97617 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/ring_buffer.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/f2099644e1b2a2c0805c5240d63ab0522d9d0174 https://git.kernel.org/stable/c/9fd4ea952e6ac12a63c3fe89f08ad02771aa2c06 https://git.kernel.org/stable/c/32bf47db9237c5b8b6f6aaa5356bb4c79d241f76 https://git.kernel.org/stable/c/d860c67c051685abb0460b593b193f0f45f4fa92