CVE-2025-68292 Details
Description
In the Linux kernel, the following vulnerability has been resolved: mm/memfd: fix information leak in hugetlb folios When allocating hugetlb folios for memfd, three initialization steps are missing: 1. Folios are not zeroed, leading to kernel memory disclosure to userspace 2. Folios are not marked uptodate before adding to page cache 3. hugetlb_fault_mutex is not taken before hugetlb_add_to_page_cache() The memfd allocation path bypasses the normal page fault handler (hugetlb_no_page) which would handle all of these initialization steps. This is problematic especially for udmabuf use cases where folios are pinned and directly accessed by userspace via DMA. Fix by matching the initialization pattern used in hugetlb_no_page(): - Zero the folio using folio_zero_user() which is optimized for huge pages - Mark it uptodate with folio_mark_uptodate() - Take hugetlb_fault_mutex before adding to page cache to prevent races The folio_zero_user() change also fixes a potential security issue where uninitialized kernel memory could be disclosed to userspace through read() or mmap() operations on the memfd.
A vulnerability in the Linux kernel's handling of hugetlb folios for memfd can lead to an information leak. When hugetlb folios are allocated for memfd, they are not properly initialized, allowing uninitialized kernel memory to be exposed to userspace. This issue arises because the memfd allocation process skips essential initialization steps that are normally managed by the page fault handler. The vulnerability is particularly concerning for udmabuf use cases, where pinned folios are accessed directly by userspace via DMA.
The vulnerability has been addressed by updating the memfd allocation process to include the missing initialization steps. This involves zeroing the folio to prevent information leaks, marking it as up-to-date before adding it to the page cache, and taking the hugetlb_fault_mutex to prevent race conditions. Users should apply the latest patches available in the Linux kernel stable tree to mitigate this vulnerability.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Dec 16, 2025References 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/50b4c1c28733a536d637d2f0401d60bcfef60ef2 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/b09d7c4dc642849d9a96753233c6d00364017fd6 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/de8798965fd0d9a6c47fc2ac57767ec32de12b49 | kernel.org | Source CodeVendor |
Weakness Enumeration
No weakness enumeration is available for this CVE.
Affected Products
| Product | Versions |
|---|---|
| Linux kernel | All versions |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 14, 2026 | CVE Translated | [email protected] |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Dec 16, 2025 | New CVE Received | kernel.org |
Volerion