Answer in brief
CVE-2022-50630 records a High severity (CVSS 7.8) vulnerability in mm: hugetlb: fix UAF in hugetlb_handle_userfault. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1a1aad8a9b7bd34f60cdf98cd7915f00ae892c45 <45c33966759ea1b4040c08dacda99ef623c0ca29 || >=1a1aad8a9b7bd34f60cdf98cd7915f00ae892c45 <0db2efb3bff879566f05341d94c3de00ac95c4cc || >=1a1aad8a9b7bd34f60cdf98cd7915f00ae892c45 <dd691973f67b2800a97db723b1ff6f07fdcf7f5a || >=1a1aad8a9b7bd34f60cdf98cd7915f00ae892c45 <78504bcedb2f1bbfb353b4d233c24d641c4dda33 || >=1a1aad8a9b7bd34f60cdf98cd7915f00ae892c45 <958f32ce832ba781ac20e11bb2d12a9352ea28fc | 45c33966759ea1b4040c08dacda99ef623c0ca29, 0db2efb3bff879566f05341d94c3de00ac95c4cc, dd691973f67b2800a97db723b1ff6f07fdcf7f5a, 78504bcedb2f1bbfb353b4d233c24d641c4dda33, 958f32ce832ba781ac20e11bb2d12a9352ea28fc |
| Linux/Linuxgeneric | 4.11 | Not reported |
Published upstream
Dec 8, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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]/
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2022-50630 records a High severity (CVSS 7.8) vulnerability in mm: hugetlb: fix UAF in hugetlb_handle_userfault. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1a1aad8a9b7bd34f60cdf98cd7915f00ae892c45 <45c33966759ea1b4040c08dacda99ef623c0ca29 || >=1a1aad8a9b7bd34f60cdf98cd7915f00ae892c45 <0db2efb3bff879566f05341d94c3de00ac95c4cc || >=1a1aad8a9b7bd34f60cdf98cd7915f00ae892c45 <dd691973f67b2800a97db723b1ff6f07fdcf7f5a || >=1a1aad8a9b7bd34f60cdf98cd7915f00ae892c45 <78504bcedb2f1bbfb353b4d233c24d641c4dda33 || >=1a1aad8a9b7bd34f60cdf98cd7915f00ae892c45 <958f32ce832ba781ac20e11bb2d12a9352ea28fc | 45c33966759ea1b4040c08dacda99ef623c0ca29, 0db2efb3bff879566f05341d94c3de00ac95c4cc, dd691973f67b2800a97db723b1ff6f07fdcf7f5a, 78504bcedb2f1bbfb353b4d233c24d641c4dda33, 958f32ce832ba781ac20e11bb2d12a9352ea28fc |
| Linux/Linuxgeneric | 4.11 | Not reported |
Published upstream
Dec 8, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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]/
Quoted source text, attributed separately from HOL analysis.