CVE-2026-23416 Details
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.
A vulnerability has been identified in the Linux kernel's memory sealing mechanism, specifically within the Virtual Memory Area (VMA) management. The issue arises because the current VMA's end position is not accurately updated during the merging process, leading to potential errors in VMA iteration. This flaw can cause the VMA handling logic to miscalculate boundaries, particularly after a VMA has been modified by flag changes that merge regions. The vulnerability affects the stable versions of the Linux kernel.
Users can upgrade to the latest stable version of the Linux kernel, where this vulnerability has been addressed. Instructions for downloading the latest kernel version are available on the official Linux kernel website.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/2697dd8ae721db4f6a53d4f4cbd438212a80f8dc | kernel.org | Patch |
| https://git.kernel.org/stable/c/40b3f4700e5535fbe74738cebb9379a40ec66bed | kernel.org | Patch |
| https://git.kernel.org/stable/c/83737e34b83a23b2a9bcf586b058b2c2a54c7c6b | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 6.17.1, < 6.18.21 >= 6.19, < 6.19.11 6.17 - 7.0 rc1 7.0 rc2 7.0 rc3 7.0 rc4 7.0 rc5 7.0 rc6 7.0 rc7 |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Apr 24, 2026 | Initial Analysis | [email protected] |
| Apr 2, 2026 | New CVE Received | kernel.org |