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 C7D9243CE65 for ; Thu, 3 Sep 2026 08:22:27 +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=1788423749; cv=none; b=MfoAWikTFyvsIpeMTX7WiOZI5o9iXSLwUBd/rMN1XysI0ouv6qy8WImp6+aBZ/zfhkrf1RVh6gOhTZg5zJNsDVpItkFOiUzzMjCJnczxL4HTltKOvMkH3z4YlpaZTbJuLUCCqbDPhyQNx1nk1BpQeFQbiziLwhd5MtGHlUl3F2w= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1788423749; c=relaxed/simple; bh=a2ufMWYNs19zlxw1rPUQWiW9xp43Xs+bGTn4H6OHPyc=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=c9FrPB0Fh66evrT3xNhTiVqjAfm1qtqmDgZI9C3qHJNuKkBmSGhdgy7e/GnvmRIhiw7JZjsA81SRElu08rb5N98vshKTcZ++i6Ml7+Eu1ZLn6KfSqcXmyHdQAlp8O5F3btHwZXImSjyzanqd8bI67zUqcb4GtlkVr/2dWAKeUhI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=wu01JqrQ; 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="wu01JqrQ" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 5C8471F00A3D; Thu, 3 Sep 2026 08:22:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1788423747; bh=WN6UnNLPB8DEl23lUE/oiX24cdU5U5nM1kjeqNOAVmo=; h=From:To:Cc:Subject:Date:Reply-To; b=wu01JqrQV6DyuZHV/uBulkRUVfd1vV/iZZcQc3h6UGEwwgEvD5fmU9OmlEgHihw8P liSBOmsT4QCfYvh7+RtsFVmjMOVKJ45IUY1Uvs451TD6TnWhCpNMDJKpO8KIX1U1Y7 2dRKGm27tyn9Hy1yCsUXN//WqYhiYiQ1hAiHE4js= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-80729: mm/huge_memory: initialise workingset state before folio split Date: Thu, 3 Sep 2026 10:21:58 +0200 Message-ID: <2026090357-CVE-2026-80729-2ad3@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=2188; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=TiruIHqUEh/ahzv1uDUqJmOVU8+L2lUI7VbZjvMdGfo=; b=owGbwMvMwCRo6H6F97bub03G02pJDFkz9VSlrqZ8tmWqM95WvKBi4VXx0vuRkY/WvQqfJfp6V pjd4cdCHbEsDIJMDLJiiixftvEc3V9xSNHL0PY0zBxWJpAhDFycAjCRG1YM80O/R7yOePjupt13 9VM8tmeO5093fsgwP/P8vLSE08ayAZoeZkY/q+vZdWQjAQ== 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: mm/huge_memory: initialise workingset state before folio split xas_try_split() adds __GFP_ACCOUNT for page-cache xa_nodes, but __folio_split() leaves the xa_state's xa_lru unset. That lets a live, memcg-charged xa_node exist without being linked into the mapping's shadow_nodes list_lru; when reclaim later walks the list_lru it trips VM_WARN_ON(!css_is_dying()). Use mapping_set_update() to install both the workingset update callback and the shadow_nodes list_lru on the xa_state. The Linux kernel CVE team has assigned CVE-2026-80729 to this issue. Affected and fixed versions =========================== Issue introduced in 6.15 with commit 58729c04cf1092b87aeef0bf0998c9e2e4771133 and fixed in 7.1.9 with commit d858f7c9fc514f1d9d3be7d00b2dd4e2f2383b55 Issue introduced in 6.15 with commit 58729c04cf1092b87aeef0bf0998c9e2e4771133 and fixed in 7.2 with commit aca1f2d5de17e138bc6c4859126b77e516b82541 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-80729 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: mm/huge_memory.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/d858f7c9fc514f1d9d3be7d00b2dd4e2f2383b55 https://git.kernel.org/stable/c/aca1f2d5de17e138bc6c4859126b77e516b82541