---
id: CVE-2026-98224
title: |-
  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…
summary: |-
  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…
severity: none
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= c84bf6dd2b836b49bb2662668ff1692350d28236 <
    fb5400bff669c8bad3d4ec09287d9b461e89e5f1
  - >-
    Linux >= c84bf6dd2b836b49bb2662668ff1692350d28236 <
    8fdc521d438fbf0d22c13d51d55d5dd82d7202b2
  - >-
    Linux >= c84bf6dd2b836b49bb2662668ff1692350d28236 <
    6cc27d82196385fe06853319f74312a7d8019726
  - Linux 6.16
published: '2026-10-06'
updated: '2026-10-06'
sourceUpdated: '2026-10-06T09:18:09.427'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-98224'
references:
  - url: 'https://git.kernel.org/stable/c/6cc27d82196385fe06853319f74312a7d8019726'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/8fdc521d438fbf0d22c13d51d55d5dd82d7202b2'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/fb5400bff669c8bad3d4ec09287d9b461e89e5f1'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
tags:
  - nvd
  - cve.org
ingestedAt: '2026-10-06T08:50:17.437Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.