CVE-2025-68293: mm/huge_memory: fix NULL pointer deference when splitting folio
In the Linux kernel, the following vulnerability has been resolved:
mm/hugememory: fix NULL pointer deference when splitting folio
Commit c010d47f107f ("mm: thp: split huge page to any lower order pages") introduced an early check on the folio's order via mapping->flags before proceeding with the split work.
This check introduced a bug: for shmem folios in the swap cache and truncated folios, the mapping pointer can be NULL. Accessing mapping->flags in this state leads directly to a NULL pointer dereference.
This commit fixes the issue by moving the check for mapping != NULL before any attempt to access mapping->flags.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Linux kernelto a version that resolves this vulnerability.Patch c010d47f107f
Event History
Frequently Asked Questions
What is the severity of CVE-2025-68293?
CVE-2025-68293 has been classified as a moderate severity vulnerability affecting the Linux kernel.
How do I fix CVE-2025-68293?
To fix CVE-2025-68293, update your Linux kernel to the latest patched version that addresses this vulnerability.
What systems are affected by CVE-2025-68293?
CVE-2025-68293 affects the Linux kernel, specifically impacting systems relying on Huge Pages.
What is the impact of CVE-2025-68293?
The vulnerability can lead to a NULL pointer dereference when splitting folio, potentially causing system crashes.
Has CVE-2025-68293 been mitigated?
Yes, CVE-2025-68293 has been mitigated with a commit in the Linux kernel that resolves the issue.