mm/vma: write lock source VMA before duplicating it in __split_vma()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 2c1393ecc3dd399561557c98d7f2e5251bb5bf92, Kernel 769417e410dd19b2a438c6addb61b194b7a4c387 and Kernel 7.3.5.
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]
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.19, >=2ab7f1bbafc927c69374d45578011c814c26ae2f <2c1393ecc3dd399561557c98d7f2e5251bb5bf92, >=2ab7f1bbafc927c69374d45578011c814c26ae2f <769417e410dd19b2a438c6addb61b194b7a4c387 | 2c1393ecc3dd399561557c98d7f2e5251bb5bf92, 769417e410dd19b2a438c6addb61b194b7a4c387 |
| linux-kernel: Kernel | >=6.19.0 <7.3.5 | 7.3.5 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket