CVE-2026-99702: mm/vma: write lock source VMA before duplicating it in __split_vma()

Published Nov 20, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

mm/vma: write lock source VMA before duplicating it in splitvma()

splitvma() duplicates the source VMA before taking its VMA write lock, and until the VMA is write-locked, a concurrent thread might set VMAMAYBEGUARDBIT, resulting in the duplication missing the flag.

If this happens, then fork may fail to duplicate guard markers and, if a file-backed mapping, THP collapse may also discard the markers.

Resolve this by taking the VMA write lock before vmareadup() and, since all callers of vmareadup() now hold the VMA write lock, assert that this is the case there, and add a comment to explain why it's needed.

[ljs@kernel.org: add VMA write assert in vmareadup(), commit message touchup]

Affected Software

3 affected componentsFixes available
linux/kernel>=6.19.0<7.3.5
7.3.5
debian/linux*
debian/linux<=7.3.4-1
6.1.176-16.1.192-26.12.107-16.12.117-17.3.5-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.5
  2. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.1.176-1Fixed in 6.1.192-2Fixed in 6.12.107-1Fixed in 6.12.117-1Fixed in 7.3.5-1

Event History

Nov 20, 2026
CVE Published
via MITRE·05:50 AM
Data Sourced
via MITRE·05:50 AM
Description
Data Sourced
via OSV·05:50 AM
DescriptionAffected Software
Data Sourced
via NVD·06:18 AM
Description

Frequently Asked Questions

1

What conditions are required for this issue to occur?

A concurrent thread must set VMA_MAYBE_GUARD_BIT after __split_vma() duplicates the source VMA but before it obtains the source VMA write lock. The resulting duplicated VMA can then miss the guard-related flag.

2

What are the practical consequences if the race occurs?

A subsequent fork may fail to duplicate guard markers. For file-backed mappings, transparent huge page collapse may also discard those markers.

3

How is the issue fixed?

The fix acquires the source VMA write lock before calling vm_area_dup(), preventing concurrent modification of the relevant flag during duplication. It also adds an assertion that callers hold the VMA write lock.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203