In the Linux kernel, the following vulnerability has been resolved: mm/vma: correctly unaccount on mmap_prepare() failure __mmap_setup() accounts memory for relevant mappings via: security_vm_enough_memory_mm() -> __vm_enough_memory() -> vm_acct_memory() If __mmap_setup() fails, this indicates that this accounting did not take place, and thus it's appropriate for __mmap_region() to jump to abort_munmap. However if call_mmap_prepare() fails, it also jumps there and any accounted memory is not correctly unaccounted. Fix this by handling each error separately.
https://git.kernel.org/stable/c/fb5400bff669c8bad3d4ec09287d9b461e89e5f1
https://git.kernel.org/stable/c/8fdc521d438fbf0d22c13d51d55d5dd82d7202b2
https://git.kernel.org/stable/c/6cc27d82196385fe06853319f74312a7d8019726