1. Home
  2. Vulnerabilities
  3. CVE-2022-50630
0.0
NA
CVE-2022-50630
mm: hugetlb: fix UAF in hugetlb_handle_userfault
Description

In the Linux kernel, the following vulnerability has been resolved: mm: hugetlb: fix UAF in hugetlb_handle_userfault The vma_lock and hugetlb_fault_mutex are dropped before handling userfault and reacquire them again after handle_userfault(), but reacquire the vma_lock could lead to UAF[1,2] due to the following race, hugetlb_fault hugetlb_no_page /*unlock vma_lock */ hugetlb_handle_userfault handle_userfault /* unlock mm->mmap_lock*/ vm_mmap_pgoff do_mmap mmap_region munmap_vma_range /* clean old vma */ /* lock vma_lock again <--- UAF */ /* unlock vma_lock */ Since the vma_lock will unlock immediately after hugetlb_handle_userfault(), let's drop the unneeded lock and unlock in hugetlb_handle_userfault() to fix the issue. [1] https://lore.kernel.org/linux-mm/[email protected]/ [2] https://lore.kernel.org/linux-mm/[email protected]/

INFO

Published Date :

Dec. 8, 2025, 2:15 a.m.

Last Modified :

Dec. 8, 2025, 2:15 a.m.

Remotely Exploit :

No

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products

The following products are affected by CVE-2022-50630 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Linux linux_kernel
: Total Affected Vendor : 1 | Products : 1
Solution
Address a use-after-free vulnerability by removing redundant locking in hugetlb_handle_userfault.
  • Remove unneeded lock and unlock in hugetlb_handle_userfault.
  • Re-evaluate locking strategy around userfault handling.
  • Apply kernel patches to address the UAF.
  • Update Linux kernel to the latest secure version.
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2022-50630.

URL Resource
https://git.kernel.org/stable/c/0db2efb3bff879566f05341d94c3de00ac95c4cc
https://git.kernel.org/stable/c/45c33966759ea1b4040c08dacda99ef623c0ca29
https://git.kernel.org/stable/c/78504bcedb2f1bbfb353b4d233c24d641c4dda33
https://git.kernel.org/stable/c/958f32ce832ba781ac20e11bb2d12a9352ea28fc
https://git.kernel.org/stable/c/dd691973f67b2800a97db723b1ff6f07fdcf7f5a
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2022-50630 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2022-50630 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2022-50630 vulnerability anywhere in the article.

Results are limited to the first 20 news articles due to potential performance issues.

The following table lists the changes that have been made to the CVE-2022-50630 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Dec. 08, 2025

    Action Type Old Value New Value
    Added Description In the Linux kernel, the following vulnerability has been resolved: mm: hugetlb: fix UAF in hugetlb_handle_userfault The vma_lock and hugetlb_fault_mutex are dropped before handling userfault and reacquire them again after handle_userfault(), but reacquire the vma_lock could lead to UAF[1,2] due to the following race, hugetlb_fault hugetlb_no_page /*unlock vma_lock */ hugetlb_handle_userfault handle_userfault /* unlock mm->mmap_lock*/ vm_mmap_pgoff do_mmap mmap_region munmap_vma_range /* clean old vma */ /* lock vma_lock again <--- UAF */ /* unlock vma_lock */ Since the vma_lock will unlock immediately after hugetlb_handle_userfault(), let's drop the unneeded lock and unlock in hugetlb_handle_userfault() to fix the issue. [1] https://lore.kernel.org/linux-mm/[email protected]/ [2] https://lore.kernel.org/linux-mm/[email protected]/
    Added Reference https://git.kernel.org/stable/c/0db2efb3bff879566f05341d94c3de00ac95c4cc
    Added Reference https://git.kernel.org/stable/c/45c33966759ea1b4040c08dacda99ef623c0ca29
    Added Reference https://git.kernel.org/stable/c/78504bcedb2f1bbfb353b4d233c24d641c4dda33
    Added Reference https://git.kernel.org/stable/c/958f32ce832ba781ac20e11bb2d12a9352ea28fc
    Added Reference https://git.kernel.org/stable/c/dd691973f67b2800a97db723b1ff6f07fdcf7f5a
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.
Vulnerability Scoring Details
No CVSS metrics available for this vulnerability.