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=1795154156; b=I+B1Do3GCf9R24yGt1e23m154K4aNg99GGRWctHaso41pWO58LRm3iWGxz/sl5wM6vQc cF4TKSSHgQua5zCSOfZAAYZkVFrfGkHohZersPeHdVfKoIHBiRWUktWYUdo7rSfHvXTmR 0Eja1UEboQYXNAUKXXrELU7DBz4WbwQs+JTL4nZRwNuTxZNK5rEug9vYdLOe9JOIVHKW8 inNewAH5tsyEyQQEjGwm4GQk6VsmpBdo2VrbQxyTUIVmObvtURrBmEUGSijKPVDH/vuCI fHltev7980JQeVjimaTl/jSCG/f1ji8y1lFPcqkjb58VtmTGoffGupHK2a2tnzhWNSg== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795154156; 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=/TDMcFA0JiYvFYdGjizI/qx7bXWY9jB5eYEauoZsEZ0=; b=dixywMCmUnr79jsHEdGGipQWX/cHH+gkhMDFmfvG0vFiyLEExfWvLoGnlqUtejJzzdQs AfrvMm2OuTne4Lpasy54mep9XJH4JrFlxRF0mH8+vjtkWV/F/ZXraXqlmwPedbJL18dLk 4hNBAdLpQjtxU+aWYx8ZXPir9UQZCLG/a414oEdXJRT8B3cnHEDpSpzCQsqmIqcFTvrd4 d2HPdmbT87WJCB9z0Pd5lUx+Hml37WdyV3sD5ghm4o/LM50AXLFWLG9vnZgCWu9avCxSZ +DKIUSZTuA2E0UYy0MdQCWbzpzYNa3egLC8K/J8LaOozaiFpfyQd/hnq6aBBQq9RI3A== 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=TaoCjMqv; 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 76354606A320 for ; Fri, 20 Nov 2026 05:55:56 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=TaoCjMqv Received: by smtp.kernel.org (Postfix) with ESMTPSA id C49961F000C4; Fri, 20 Nov 2026 05:55:55 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795154156; bh=/TDMcFA0JiYvFYdGjizI/qx7bXWY9jB5eYEauoZsEZ0=; h=From:To:Cc:Subject:Date:Reply-To; b=TaoCjMqvcjpR/6/9wJai88DBCYIgl09Vheiy0ZKvFzY5fIRt35x+JDww06dYHVsm8 aZZoOGVNfNMZOX/JozXKavCLvv2fMicldz8PDZ+lHX3dGpmP0Zr5wqwLFmg44sE4l7 wG26mA1Oi+Fuk3tXKdFl051mIrPMLcndEjnkX1ac= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99646: mm/vma: don't leak the charge for stack growth Date: Fri, 20 Nov 2026 06:50:32 +0100 Message-ID: <2026112042-CVE-2026-99646-7ccb@gregkh> X-Mailer: git-send-email 2.56.1 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=2149; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=XA/OLiAiYP0h0RxF74BhnLSHWBLWRa3+igtNZiHNpkA=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/75eZP1qQvnOf/b6DHxJ8L3oX3eo7FSbLEbX+hL3/Z W/uAMmDHbEsDIJMDLJiiixftvEc3V9xSNHL0PY0zBxWJpAhDFycAjAR6bMMCzbUWXwJd31opleZ O/1J75OTJ578nsawoOOIbM+3w07fey1l5m41MdHuqylpBwA= 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/vma: don't leak the charge for stack growth acct_stack_growth() charges stack expansion even without VM_ACCOUNT. This can happen for read-only or MAP_NORESERVE mappings created with MAP_GROWSDOWN. Unmapping these VMAs does not release the charge, leaking Committed_AS. Only check and charge growth for VM_ACCOUNT VMAs, matching mremap(). Unaccounted growth skips the overcommit check while remaining subject to the other stack-growth limits. The Linux kernel CVE team has assigned CVE-2026-99646 to this issue. Affected and fixed versions =========================== Issue introduced in 2.6.12 with commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and fixed in 7.3.5 with commit 1dd99ffea63f3ef82fda213beb3b9b2f9dc41674 Issue introduced in 2.6.12 with commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and fixed in 7.4-rc2 with commit b1ee87802111156e27557e82acc31fa7dfc76e2a 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-99646 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/vma.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/1dd99ffea63f3ef82fda213beb3b9b2f9dc41674 https://git.kernel.org/stable/c/b1ee87802111156e27557e82acc31fa7dfc76e2a