CVE-2026-99646: mm/vma: don't leak the charge for stack growth
In the Linux kernel, the following vulnerability has been resolved:
mm/vma: don't leak the charge for stack growth
acctstackgrowth() charges stack expansion even without VMACCOUNT. This can happen for read-only or MAPNORESERVE mappings created with MAPGROWSDOWN. Unmapping these VMAs does not release the charge, leaking CommittedAS.
Only check and charge growth for VMACCOUNT VMAs, matching mremap(). Unaccounted growth skips the overcommit check while remaining subject to the other stack-growth limits.
Affected Software
Frequently Asked Questions
Which mappings can trigger the leaked commit accounting?
The issue can occur with MAP_GROWSDOWN mappings that are read-only or created with MAP_NORESERVE, because their stack growth can be charged despite not having VM_ACCOUNT.
What is the practical impact of repeated triggering?
Unmapping the affected VMAs does not release the stack-growth charge, so Committed_AS can accumulate over time. This can cause commit accounting to remain artificially elevated.
Are normal stack-growth limits bypassed by the fix?
No. For VMAs without VM_ACCOUNT, growth skips the overcommit check but remains subject to the other stack-growth limits.
How can an administrator identify possible exposure?
Look for workloads that create MAP_GROWSDOWN mappings with read-only protection or MAP_NORESERVE and then grow and unmap them. A Committed_AS value that remains elevated after those mappings are unmapped is consistent with the issue.