CVE-2024-50263 Details
Description
In the Linux kernel, the following vulnerability has been resolved: fork: only invoke khugepaged, ksm hooks if no error There is no reason to invoke these hooks early against an mm that is in an incomplete state. The change in commit d24062914837 ("fork: use __mt_dup() to duplicate maple tree in dup_mmap()") makes this more pertinent as we may be in a state where entries in the maple tree are not yet consistent. Their placement early in dup_mmap() only appears to have been meaningful for early error checking, and since functionally it'd require a very small allocation to fail (in practice 'too small to fail') that'd only occur in the most dire circumstances, meaning the fork would fail or be OOM'd in any case. Since both khugepaged and KSM tracking are there to provide optimisations to memory performance rather than critical functionality, it doesn't really matter all that much if, under such dire memory pressure, we fail to register an mm with these. As a result, we follow the example of commit d2081b2bf819 ("mm: khugepaged: make khugepaged_enter() void function") and make ksm_fork() a void function also. We only expose the mm to these functions once we are done with them and only if no error occurred in the fork operation.
A use-after-free vulnerability has been identified in the Linux kernel, specifically in versions 6.8-rc1 and later. This issue arises in the memory management subsystem during the process of forking, particularly when the 'khugepaged' or 'userfaultfd' features are involved. The vulnerability was introduced by a commit that optimized the forking process by creating a shallow copy of the parent's virtual memory areas (VMAs). If an error occurs during this process, the VMA entries can be left in an inconsistent state. Meanwhile, 'khugepaged' or 'userfaultfd' can access these nascent VMAs, leading to a use-after-free condition.
Users can upgrade to Linux kernel version 6.11.7 or later, where this vulnerability has been fixed.
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/3b85aa0da8cd01173b9afd1f70080fbb9576c4b0 | kernel.org | Patch |
| https://git.kernel.org/stable/c/985da552a98e27096444508ce5d853244019111f | kernel.org | Patch |
| https://project-zero.issues.chromium.org/issues/373391951 | kernel.org |
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.8, < 6.11.7 6.12 rc1 6.12 rc2 6.12 rc3 6.12 rc4 6.12 rc5 |
CPE
Remediation
| |
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Aug 4, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Dec 9, 2024 | CVE Modified | kernel.org |
| Nov 14, 2024 | Initial Analysis | [email protected] |
| Nov 11, 2024 | New CVE Received | kernel.org |