Skip to main content
VulnerabilityPublished

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

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-99702· Medium

Not known to be exploited : upgrade to 769417e410dd19b2a438c6addb61b194b7a4c387 or 2c1393ecc3dd399561557c98d7f2e5251bb5bf92 when convenient.

Data as of 20 Nov 2026, 07:34 UTC

Severity
Medium

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 769417e410dd19b2a438c6addb61b194b7a4c387, 2c1393ecc3dd399561557c98d7f2e5251bb5bf92

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade Linux kernel to 769417e410dd19b2a438c6addb61b194b7a4c387 or 2c1393ecc3dd399561557c98d7f2e5251bb5bf92.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 2ab7f1bbafc927c69374d45578011c814c26ae2f, < 769417e410dd19b2a438c6addb61b194b7a4c387
Fixed in
  • 769417e410dd19b2a438c6addb61b194b7a4c387
LinuxLinuxAffected
  • ≥ 2ab7f1bbafc927c69374d45578011c814c26ae2f, < 2c1393ecc3dd399561557c98d7f2e5251bb5bf92
Fixed in
  • 2c1393ecc3dd399561557c98d7f2e5251bb5bf92
LinuxLinuxAffected
  • =6.19
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: mm/vma: write lock source VMA before duplicating it in __split_vma() __split_vma() duplicates the source VMA before taking its VMA write lock, and until the VMA is write-locked, a concurrent thread might set VMA_MAYBE_GUARD_BIT, 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 vm_area_dup() and, since all callers of vm_area_dup() 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 vm_area_dup(), commit message touchup]

References

Community reviews

Loading reviews…