Bug 2577696 (CVE-2026-99702) - CVE-2026-99702 kernel: kernel: memory protection bypass via race condition in virtual memory area splitting
Summary: CVE-2026-99702 kernel: kernel: memory protection bypass via race condition in...
Keywords:
Status: NEW
Alias: CVE-2026-99702
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-11-20 06:08 UTC by OSIDB Bzimport
Modified: 2026-11-20 10:25 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-11-20 06:08:48 UTC
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: add VMA write assert in vm_area_dup(), commit message touchup]


Note You need to log in before you can comment on or make changes to this bug.