CVE-2025-68292
BaseFortify
Publication date: 2025-12-16
Last updated on: 2025-12-18
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in the Linux kernel involves the memfd subsystem when allocating hugetlb folios. Three initialization steps were missing: the folios were not zeroed, not marked uptodate before adding to the page cache, and a necessary mutex was not taken before adding to the page cache. Because of this, uninitialized kernel memory could be disclosed to userspace, especially in use cases where folios are pinned and accessed directly by userspace via DMA. The fix involves zeroing the folios, marking them uptodate, and taking the mutex to prevent race conditions.
How can this vulnerability impact me? :
This vulnerability can lead to information leakage where uninitialized kernel memory is exposed to userspace processes. This could allow an attacker or malicious userspace application to read sensitive kernel memory contents through read() or mmap() operations on memfd, potentially compromising system security and confidentiality.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, update your Linux kernel to a version that includes the fix for the memfd hugetlb folios initialization issue. The fix involves zeroing the folios, marking them uptodate before adding to the page cache, and taking the hugetlb_fault_mutex to prevent races. Applying the kernel patch or upgrading to a fixed kernel version will prevent kernel memory disclosure to userspace.