mm/vma: correctly unaccount on mmap_prepare() failure
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.18.547.2.87.3In 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.
From the CVE record · Linux
The Linux kernel does not correctly undo memory accounting when call_mmap_prepare() fails. The input does not describe how an attacker could trigger or exploit this issue, or specify access or user-interaction requirements.
Engineers running Linux kernels should check their versions against the vendor advisory; affected versions were not provided.