{"api_version":"1","generated_at":"2026-04-20T15:20:33+00:00","cve":"CVE-2026-23416","urls":{"html":"https://cve.report/CVE-2026-23416","api":"https://cve.report/api/cve/CVE-2026-23416.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-23416","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-23416"},"summary":{"title":"mm/mseal: update VMA end correctly on merge","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nmm/mseal: update VMA end correctly on merge\n\nPreviously we stored the end of the current VMA in curr_end, and then upon\niterating to the next VMA updated curr_start to curr_end to advance to the\nnext VMA.\n\nHowever, this doesn't take into account the fact that a VMA might be\nupdated due to a merge by vma_modify_flags(), which can result in curr_end\nbeing stale and thus, upon setting curr_start to curr_end, ending up with\nan incorrect curr_start on the next iteration.\n\nResolve the issue by setting curr_end to vma->vm_end unconditionally to\nensure this value remains updated should this occur.\n\nWhile we're here, eliminate this entire class of bug by simply setting\nconst curr_[start/end] to be clamped to the input range and VMAs, which\nalso happens to simplify the logic.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-04-02 12:16:20","updated_at":"2026-04-03 16:10:52"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/2697dd8ae721db4f6a53d4f4cbd438212a80f8dc","name":"https://git.kernel.org/stable/c/2697dd8ae721db4f6a53d4f4cbd438212a80f8dc","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/83737e34b83a23b2a9bcf586b058b2c2a54c7c6b","name":"https://git.kernel.org/stable/c/83737e34b83a23b2a9bcf586b058b2c2a54c7c6b","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/40b3f4700e5535fbe74738cebb9379a40ec66bed","name":"https://git.kernel.org/stable/c/40b3f4700e5535fbe74738cebb9379a40ec66bed","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-23416","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23416","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6c2da14ae1e0a0146587381594559027bd46c059 40b3f4700e5535fbe74738cebb9379a40ec66bed git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6c2da14ae1e0a0146587381594559027bd46c059 83737e34b83a23b2a9bcf586b058b2c2a54c7c6b git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6c2da14ae1e0a0146587381594559027bd46c059 2697dd8ae721db4f6a53d4f4cbd438212a80f8dc git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.17","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.17 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.21 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.19.11 6.19.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.0-rc6 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"23416","cve":"CVE-2026-23416","epss":"0.000070000","percentile":"0.005720000","score_date":"2026-04-07","updated_at":"2026-04-08 00:03:39"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["mm/mseal.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"40b3f4700e5535fbe74738cebb9379a40ec66bed","status":"affected","version":"6c2da14ae1e0a0146587381594559027bd46c059","versionType":"git"},{"lessThan":"83737e34b83a23b2a9bcf586b058b2c2a54c7c6b","status":"affected","version":"6c2da14ae1e0a0146587381594559027bd46c059","versionType":"git"},{"lessThan":"2697dd8ae721db4f6a53d4f4cbd438212a80f8dc","status":"affected","version":"6c2da14ae1e0a0146587381594559027bd46c059","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["mm/mseal.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.17"},{"lessThan":"6.17","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.21","versionType":"semver"},{"lessThanOrEqual":"6.19.*","status":"unaffected","version":"6.19.11","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.0-rc6","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.21","versionStartIncluding":"6.17","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.19.11","versionStartIncluding":"6.17","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.0-rc6","versionStartIncluding":"6.17","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nmm/mseal: update VMA end correctly on merge\n\nPreviously we stored the end of the current VMA in curr_end, and then upon\niterating to the next VMA updated curr_start to curr_end to advance to the\nnext VMA.\n\nHowever, this doesn't take into account the fact that a VMA might be\nupdated due to a merge by vma_modify_flags(), which can result in curr_end\nbeing stale and thus, upon setting curr_start to curr_end, ending up with\nan incorrect curr_start on the next iteration.\n\nResolve the issue by setting curr_end to vma->vm_end unconditionally to\nensure this value remains updated should this occur.\n\nWhile we're here, eliminate this entire class of bug by simply setting\nconst curr_[start/end] to be clamped to the input range and VMAs, which\nalso happens to simplify the logic."}],"providerMetadata":{"dateUpdated":"2026-04-02T11:40:57.158Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/40b3f4700e5535fbe74738cebb9379a40ec66bed"},{"url":"https://git.kernel.org/stable/c/83737e34b83a23b2a9bcf586b058b2c2a54c7c6b"},{"url":"https://git.kernel.org/stable/c/2697dd8ae721db4f6a53d4f4cbd438212a80f8dc"}],"title":"mm/mseal: update VMA end correctly on merge","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-23416","datePublished":"2026-04-02T11:40:57.158Z","dateReserved":"2026-01-13T15:37:46.014Z","dateUpdated":"2026-04-02T11:40:57.158Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-04-02 12:16:20","lastModifiedDate":"2026-04-03 16:10:52","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"23416","Ordinal":"1","Title":"mm/mseal: update VMA end correctly on merge","CVE":"CVE-2026-23416","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"23416","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nmm/mseal: update VMA end correctly on merge\n\nPreviously we stored the end of the current VMA in curr_end, and then upon\niterating to the next VMA updated curr_start to curr_end to advance to the\nnext VMA.\n\nHowever, this doesn't take into account the fact that a VMA might be\nupdated due to a merge by vma_modify_flags(), which can result in curr_end\nbeing stale and thus, upon setting curr_start to curr_end, ending up with\nan incorrect curr_start on the next iteration.\n\nResolve the issue by setting curr_end to vma->vm_end unconditionally to\nensure this value remains updated should this occur.\n\nWhile we're here, eliminate this entire class of bug by simply setting\nconst curr_[start/end] to be clamped to the input range and VMAs, which\nalso happens to simplify the logic.","Type":"Description","Title":"mm/mseal: update VMA end correctly on merge"}]}}}