CVE Feed
— Unscored

In the Linux kernel, the following vulnerability has been resolved: mm/vma: write lock source VMA before duplicating it in splitvma()…

CVE-2026-99702

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]

Assessment

CVSS
Not yet scored
Severity
Unscored
Known exploited
Not listed in CISA KEV
Exploit availability
Nothing found in Exploit-DB, Metasploit, Nuclei or public PoC repositories
Published
20 November 2026
Last updated
20 November 2026
Affected
Linux · Linux
Assigner
Linux

At the source

References

Community proofs of concept

No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.

Submit a proof of concept
Before you submit *

Query this programmatically

Agents can read this through the MCP endpoint, or over HTTP:

curl https://cve.zerocrew.in/api/cve/CVE-2026-99702