CVE-2026-99702: Linux kernel · mm/vma: write lock source VMA before duplicating it in __split_vma()
Affects Linux kernelSource CVE Database V5
Not known to be exploited : upgrade to 769417e410dd19b2a438c6addb61b194b7a4c387 or 2c1393ecc3dd399561557c98d7f2e5251bb5bf92 when convenient.
Data as of 20 Nov 2026, 06:37 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 769417e410dd19b2a438c6addb61b194b7a4c387, 2c1393ecc3dd399561557c98d7f2e5251bb5bf92
Exploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available and has been applied in the Linux kernel. The vulnerability is resolved by acquiring the VMA write lock before duplicating the VMA in __split_vma(). Users and administrators should update to the fixed kernel versions identified by the commits 769417e410dd19b2a438c6addb61b194b7a4c387 and 2c1393ecc3dd399561557c98d7f2e5251bb5bf92 to mitigate this issue.
Description
A vulnerability in the Linux kernel's memory management subsystem was fixed by ensuring the source Virtual Memory Area (VMA) is write-locked before duplication in the __split_vma() function. Previously, the duplication occurred before acquiring the write lock, allowing a concurrent thread to modify flags, causing fork operations to fail to duplicate guard markers correctly and potentially leading to Transparent Huge Page (THP) collapse discarding these markers in file-backed mappings.