Skip to content
Heist/ feed
Back to feed
UnratedFix available

mm/mseal: update VMA end correctly on merge

Type: advisorySources: OSV

In the Linux kernel, the following vulnerability has been resolved: mm/mseal: update VMA end correctly on merge Previously we stored the end of the current VMA in curr_end, and then upon iterating to the next VMA updated curr_start to curr_end to advance to the next VMA. However, this doesn't take into account the fact that a VMA might be updated due to a merge by vma_modify_flags(), which can result in curr_end being stale and thus, upon setting curr_start to curr_end, ending up with an incorrect curr_start on the next iteration. Resolve the issue by setting curr_end to vma->vm_end unconditionally to ensure this value remains updated should this occur. While we're here, eliminate this entire class of bug by simply setting const curr_[start/end] to be clamped to the input range and VMAs, which also happens to simplify the logic.

Products
Kernel
Affected versions
Not specified
Fixed versions
6.18.21, 6.19.11
CVEs
CVE-2026-23416
Confirmed fixed CVEs
Not specified
Updated in this feed
4 Nov 2026, 16:13 UTC · Revision 1

Source evidence

mm/mseal: update VMA end correctly on merge

core-osv · Original source

Published 2 Apr 2026, 11:40 UTC

In the Linux kernel, the following vulnerability has been resolved: mm/mseal: update VMA end correctly on merge Previously we stored the end of the current VMA in curr_end, and then upon iterating to the next VMA updated curr_start to curr_end to advance to the next VMA. However, this doesn't take into account the fact that a VMA might be updated due to a merge by vma_modify_flags(), which can result in curr_end being stale and thus, upon setting curr_start to curr_end, ending up with an incorrect curr_start on the next iteration. Resolve the issue by setting curr_end to vma->vm_end unconditionally to ensure this value remains updated should this occur. While we're here, eliminate this entire class of bug by simply setting const curr_[start/end] to be clamped to the input range and VMAs, which also happens to simplify the logic.

osv:CVE-2026-23416

Kernel

Fixed versions: 6.18.21, 6.19.11

Complete source record
{
  "id": "64ae5fc8f3447c77c2e46f1e8fc834b3941af3c871f461abdcf050a48791e4e8",
  "url": "https://osv.dev/vulnerability/CVE-2026-23416",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "mm/mseal: update VMA end correctly on merge",
    "summary": "In the Linux kernel, the following vulnerability has been resolved: mm/mseal: update VMA end correctly on merge Previously we stored the end of the current VMA in curr_end, and then upon iterating to the next VMA updated curr_start to curr_end to advance to the next VMA. However, this doesn't take into account the fact that a VMA might be updated due to a merge by vma_modify_flags(), which can result in curr_end being stale and thus, upon setting curr_start to curr_end, ending up with an incorrect curr_start on the next iteration. Resolve the issue by setting curr_end to vma->vm_end unconditionally to ensure this value remains updated should this occur. While we're here, eliminate this entire class of bug by simply setting const curr_[start/end] to be clamped to the input range and VMAs, which also happens to simplify the logic.",
    "evidence": "osv:CVE-2026-23416",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "6.18.21",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.19.11",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "unknown",
    "structured": {
      "id": "CVE-2026-23416",
      "aliases": [
        "CVE-2026-23416"
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "6c2da14ae1e0a0146587381594559027bd46c059"
                },
                {
                  "fixed": "40b3f4700e5535fbe74738cebb9379a40ec66bed"
                },
                {
                  "fixed": "83737e34b83a23b2a9bcf586b058b2c2a54c7c6b"
                },
                {
                  "fixed": "2697dd8ae721db4f6a53d4f4cbd438212a80f8dc"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-23416.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.17.0"
                },
                {
                  "fixed": "6.18.21"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.19.0"
                },
                {
                  "fixed": "6.19.11"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-23416.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:37.451342968Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/2697dd8ae721db4f6a53d4f4cbd438212a80f8dc",
        "https://git.kernel.org/stable/c/40b3f4700e5535fbe74738cebb9379a40ec66bed",
        "https://git.kernel.org/stable/c/83737e34b83a23b2a9bcf586b058b2c2a54c7c6b",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/23xxx/CVE-2026-23416.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2026-23416",
        "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
      ],
      "provider_metadata": {
        "cna_assigner": "Linux",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/23xxx/CVE-2026-23416.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-23416",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": null
  },
  "source_id": "core-osv",
  "document_id": 504540,
  "published_at": "2026-04-02T11:40:57.158+00:00"
}