Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-23416mm/mseal: update VMA end correctly on merge

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 3 months later

    Published

  3. · 39 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-23416, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.22% · top 87% of all CVEs (18 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 6c2da14ae1e0a0146587381594559027bd46c059 – < 40b3f4700e5535fbe74738cebb9379a40ec66bed
    • affected 6c2da14ae1e0a0146587381594559027bd46c059 – < 83737e34b83a23b2a9bcf586b058b2c2a54c7c6b
    • affected 6c2da14ae1e0a0146587381594559027bd46c059 – < 2697dd8ae721db4f6a53d4f4cbd438212a80f8dc
  • Linux · Linux

    • affected 6.17
    • unaffected < 6.17
    • unaffected 6.18.21 – ≤ 6.18.*
    • unaffected 6.19.11 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References3

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-23416 badge
[![CVE-2026-23416](https://cveledger.app/badge/CVE-2026-23416.svg)](https://cveledger.app/cve/CVE-2026-23416)

Record last updated .