CVE-2026-46318 Details
Description
In the Linux kernel, the following vulnerability has been resolved: Revert "mm/hugetlbfs: update hugetlbfs to use mmap_prepare" This reverts commit ea52cb24cd3f ("mm/hugetlbfs: update hugetlbfs to use mmap_prepare") with conflict resolution to account for changes in commit ea52cb24cd3f ("mm/hugetlbfs: update hugetlbfs to use mmap_prepare"). The patch incorrectly handled hugetlb VMA lock allocation at the mmap_prepare stage, where a failed allocation occurring after mmap_prepare is called might result in the lock leaking. There is no risk of a merge causing a similar issues, as VMA_DONTEXPAND_BIT is set for hugetlb mappings. As a first step in addressing this issue, simply revert the change so we can rework how we do this having corrected the underlying issues. We maintain the VMA flags changes as best we can, accounting for the fact that we were working with a VMA descriptor previously and propagating like-for-like changes for this. Note that we invoke vma_set_flags() and do not call vma_start_write() as vm_flags_set() does. This is OK as it's being done in an .mmap hook where the VMA is not yet linked into the tree so nobody else can be accessing it.
A vulnerability in the Linux kernel's handling of HugeTLB (large page) memory management has been addressed. The issue arose from a patch that modified how HugeTLB file mappings were prepared for memory mapping operations. This change inadvertently disrupted the allocation of locks needed for managing HugeTLB virtual memory areas (VMAs). When the allocation process failed after the VMA was prepared, it could lead to a lock being improperly released, creating a potential synchronization issue. Although this vulnerability could cause a lock to leak, it is not expected to result in a similar problem during a merge, as HugeTLB mappings are configured to prevent expansion conflicts. The vulnerability has been resolved by reverting the problematic patch and restoring the previous VMA lock allocation process, ensuring that locks are correctly managed without introducing conflicts.
Users can apply the latest patches from the Linux kernel stable tree to address this vulnerability.
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/3af5fc3f0ac98c624c109c8c0796fa46e814344c | kernel.org | Patch |
| https://git.kernel.org/stable/c/83f9efcce93f8574be2279090ee2aec58b86cda7 | 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.19, < 7.0.12 7.1 rc1 7.1 rc2 7.1 rc3 7.1 rc4 7.1 rc5 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jul 23, 2026 | CVE Translated | [email protected] |
| Jul 8, 2026 | Initial Analysis | [email protected] |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Jun 9, 2026 | New CVE Received | kernel.org |