{"api_version":"1","generated_at":"2026-11-20T07:29:58+00:00","cve":"CVE-2026-99702","urls":{"html":"https://cve.report/CVE-2026-99702","api":"https://cve.report/api/cve/CVE-2026-99702.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-99702","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-99702"},"summary":{"title":"mm/vma: write lock source VMA before duplicating it in __split_vma()","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nmm/vma: write lock source VMA before duplicating it in __split_vma()\n\n__split_vma() duplicates the source VMA before taking its VMA write lock,\nand until the VMA is write-locked, a concurrent thread might set\nVMA_MAYBE_GUARD_BIT, resulting in the duplication missing the flag.\n\nIf this happens, then fork may fail to duplicate guard markers and, if a\nfile-backed mapping, THP collapse may also discard the markers.\n\nResolve this by taking the VMA write lock before vm_area_dup() and, since\nall callers of vm_area_dup() now hold the VMA write lock, assert that this\nis the case there, and add a comment to explain why it's needed.\n\n[ljs@kernel.org: add VMA write assert in vm_area_dup(), commit message touchup]","state":"PUBLISHED","assigner":"Linux","published_at":"2026-11-20 06:18:05","updated_at":"2026-11-20 06:18:05"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/769417e410dd19b2a438c6addb61b194b7a4c387","name":"https://git.kernel.org/stable/c/769417e410dd19b2a438c6addb61b194b7a4c387","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/2c1393ecc3dd399561557c98d7f2e5251bb5bf92","name":"https://git.kernel.org/stable/c/2c1393ecc3dd399561557c98d7f2e5251bb5bf92","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-99702","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99702","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 2ab7f1bbafc927c69374d45578011c814c26ae2f 2c1393ecc3dd399561557c98d7f2e5251bb5bf92 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 2ab7f1bbafc927c69374d45578011c814c26ae2f 769417e410dd19b2a438c6addb61b194b7a4c387 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.19","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.19 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3.5 7.3.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.4-rc2 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["mm/vma.c","mm/vma_init.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"2c1393ecc3dd399561557c98d7f2e5251bb5bf92","status":"affected","version":"2ab7f1bbafc927c69374d45578011c814c26ae2f","versionType":"git"},{"lessThan":"769417e410dd19b2a438c6addb61b194b7a4c387","status":"affected","version":"2ab7f1bbafc927c69374d45578011c814c26ae2f","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["mm/vma.c","mm/vma_init.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.19"},{"lessThan":"6.19","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"7.3.*","status":"unaffected","version":"7.3.5","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.4-rc2","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3.5","versionStartIncluding":"6.19","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.4-rc2","versionStartIncluding":"6.19","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nmm/vma: write lock source VMA before duplicating it in __split_vma()\n\n__split_vma() duplicates the source VMA before taking its VMA write lock,\nand until the VMA is write-locked, a concurrent thread might set\nVMA_MAYBE_GUARD_BIT, resulting in the duplication missing the flag.\n\nIf this happens, then fork may fail to duplicate guard markers and, if a\nfile-backed mapping, THP collapse may also discard the markers.\n\nResolve this by taking the VMA write lock before vm_area_dup() and, since\nall callers of vm_area_dup() now hold the VMA write lock, assert that this\nis the case there, and add a comment to explain why it's needed.\n\n[ljs@kernel.org: add VMA write assert in vm_area_dup(), commit message touchup]"}],"providerMetadata":{"dateUpdated":"2026-11-20T05:50:44.005Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/2c1393ecc3dd399561557c98d7f2e5251bb5bf92"},{"url":"https://git.kernel.org/stable/c/769417e410dd19b2a438c6addb61b194b7a4c387"}],"title":"mm/vma: write lock source VMA before duplicating it in __split_vma()","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-99702","datePublished":"2026-11-20T05:50:44.005Z","dateReserved":"2026-09-25T10:25:14.429Z","dateUpdated":"2026-11-20T05:50:44.005Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-11-20 06:18:05","lastModifiedDate":"2026-11-20 06:18:05","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"99702","Ordinal":"1","Title":"mm/vma: write lock source VMA before duplicating it in __split_v","CVE":"CVE-2026-99702","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"99702","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nmm/vma: write lock source VMA before duplicating it in __split_vma()\n\n__split_vma() duplicates the source VMA before taking its VMA write lock,\nand until the VMA is write-locked, a concurrent thread might set\nVMA_MAYBE_GUARD_BIT, resulting in the duplication missing the flag.\n\nIf this happens, then fork may fail to duplicate guard markers and, if a\nfile-backed mapping, THP collapse may also discard the markers.\n\nResolve this by taking the VMA write lock before vm_area_dup() and, since\nall callers of vm_area_dup() now hold the VMA write lock, assert that this\nis the case there, and add a comment to explain why it's needed.\n\n[ljs@kernel.org: add VMA write assert in vm_area_dup(), commit message touchup]","Type":"Description","Title":"mm/vma: write lock source VMA before duplicating it in __split_v"}]}}}