PT-2026-152582

CVE-2026-99702

·

Published

2026-11-20

·

Updated

2026-11-20

Description by

Score
N/A
Not available

No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.

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]
Vendors
Affected products
Related identifiers
Found an issue in the description? Have something to add? Feel free to write us 👾