CVE-2022-50630

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-12-08. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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]/

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

December 8, 2025

Last Modified

August 5, 2026

Advisory Details (5)

Auto-updated Aug 4, 2026
No patch confirmed yet.
generic

mm: hugetlb: fix UAF in hugetlb_handle_userfault - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/dd691973f67b2800a97db723b1ff6f07fdcf7f5a
generic

mm: hugetlb: fix UAF in hugetlb_handle_userfault - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/958f32ce832ba781ac20e11bb2d12a9352ea28fc
generic

mm: hugetlb: fix UAF in hugetlb_handle_userfault - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/78504bcedb2f1bbfb353b4d233c24d641c4dda33
generic

mm: hugetlb: fix UAF in hugetlb_handle_userfault - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/45c33966759ea1b4040c08dacda99ef623c0ca29
generic

mm: hugetlb: fix UAF in hugetlb_handle_userfault - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0db2efb3bff879566f05341d94c3de00ac95c4cc

Vendor Advisories for CVE-2022-50630(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:5.14.0-362.8.1.el9_32023-11-07redhat
linuxKernel @ 5.10.150—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Data Freshness Timeline

(refreshed 15× in last 7d / 51× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 155 total refreshes for this CVE.

  1. 2026-08-05 19:15 UTCEPSS rescore
  2. 2026-08-05 09:19 UTCEG score recompute
  3. 2026-08-05 09:19 UTCGHSA enrichment
  4. 2026-08-04 15:07 UTCEPSS rescore
  5. 2026-08-04 10:56 UTCEG score recompute
  6. 2026-08-04 10:55 UTCGHSA enrichment
  7. 2026-08-04 10:35 UTCEPSS rescore
  8. 2026-08-04 09:27 UTCEG score recompute▲ 7.80
  9. 2026-08-04 09:27 UTCGHSA enrichment
  10. 2026-08-04 09:20 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  11. 2026-08-03 10:33 UTCEPSS rescore
  12. 2026-08-02 02:24 UTCEPSS rescore
  13. 2026-08-01 04:13 UTCEPSS rescore
  14. 2026-08-01 04:13 UTCEPSS rescore
  15. 2026-07-30 16:25 UTCEPSS rescore
  16. 2026-07-30 01:28 UTCEPSS rescore
  17. 2026-07-28 15:34 UTCEPSS rescore
  18. 2026-07-27 05:39 UTCOSV refresh
  19. 2026-07-26 14:52 UTCEPSS rescore
  20. 2026-07-26 14:52 UTCEPSS rescore
  21. 2026-07-25 14:16 UTCEPSS rescore
  22. 2026-07-24 14:15 UTCEPSS rescore
  23. 2026-07-23 14:16 UTCEPSS rescore
  24. 2026-07-23 14:16 UTCEPSS rescore
  25. 2026-07-23 02:17 UTCEG score recompute
Show 75 more
  1. 2026-07-22 23:04 UTCEG score recompute
  2. 2026-07-22 14:06 UTCEPSS rescore
  3. 2026-07-22 14:06 UTCEPSS rescore
  4. 2026-07-21 15:23 UTCEPSS rescore
  5. 2026-07-21 15:23 UTCEPSS rescore
  6. 2026-07-20 17:05 UTCEPSS rescore
  7. 2026-07-19 14:29 UTCEPSS rescore
  8. 2026-07-19 14:29 UTCEPSS rescore
  9. 2026-07-19 02:27 UTCEPSS rescore
  10. 2026-07-19 02:27 UTCEPSS rescore
  11. 2026-07-18 10:03 UTCEPSS rescore
  12. 2026-07-18 10:03 UTCEPSS rescore
  13. 2026-07-16 17:00 UTCEPSS rescore
  14. 2026-07-15 16:56 UTCEPSS rescore
  15. 2026-07-15 16:56 UTCEPSS rescore
  16. 2026-07-15 01:58 UTCEPSS rescore
  17. 2026-07-15 01:58 UTCEPSS rescore
  18. 2026-07-13 22:28 UTCEPSS rescore
  19. 2026-07-13 22:28 UTCEPSS rescore
  20. 2026-07-13 06:11 UTCEPSS rescore
  21. 2026-07-13 06:11 UTCEPSS rescore
  22. 2026-07-12 05:44 UTCEPSS rescore
  23. 2026-07-10 00:17 UTCOSV refresh
  24. 2026-07-09 19:08 UTCEPSS rescore
  25. 2026-07-08 15:13 UTCEPSS rescore
  26. 2026-07-07 13:44 UTCEPSS rescore
  27. 2026-07-06 02:21 UTCEPSS rescore
  28. 2026-07-05 02:28 UTCEPSS rescore
  29. 2026-07-04 06:29 UTCEPSS rescore
  30. 2026-07-01 15:04 UTCEPSS rescore
  31. 2026-06-30 23:21 UTCEPSS rescore
  32. 2026-06-30 23:20 UTCEPSS rescore
  33. 2026-06-29 14:04 UTCEPSS rescore
  34. 2026-06-28 14:06 UTCEPSS rescore
  35. 2026-06-28 04:54 UTCEPSS rescore
  36. 2026-06-28 04:54 UTCEPSS rescore
  37. 2026-06-27 03:07 UTCEPSS rescore
  38. 2026-06-27 03:07 UTCEPSS rescore
  39. 2026-06-25 13:48 UTCEPSS rescore
  40. 2026-06-25 13:48 UTCEPSS rescore
  41. 2026-06-24 14:03 UTCEPSS rescore
  42. 2026-06-24 14:03 UTCEPSS rescore
  43. 2026-06-23 21:31 UTCEPSS rescore
  44. 2026-06-23 21:31 UTCEPSS rescore
  45. 2026-06-22 14:24 UTCEPSS rescore
  46. 2026-06-21 14:55 UTCEPSS rescore
  47. 2026-06-21 14:55 UTCEPSS rescore
  48. 2026-06-21 11:01 UTCOSV refresh
  49. 2026-06-21 01:58 UTCEPSS rescore
  50. 2026-06-21 01:58 UTCEPSS rescore
  51. 2026-06-19 19:24 UTCEPSS rescore
  52. 2026-06-19 19:24 UTCEPSS rescore
  53. 2026-06-18 17:51 UTCEPSS rescore
  54. 2026-06-18 17:51 UTCEPSS rescore
  55. 2026-06-17 17:51 UTCEPSS rescore
  56. 2026-06-17 17:51 UTCEPSS rescore
  57. 2026-06-16 17:51 UTCEPSS rescore
  58. 2026-06-16 17:51 UTCEPSS rescore
  59. 2026-06-15 17:47 UTCEPSS rescore
  60. 2026-06-14 23:16 UTCEPSS rescore
  61. 2026-06-13 22:59 UTCEPSS rescore
  62. 2026-06-12 23:10 UTCEPSS rescore
  63. 2026-06-12 23:10 UTCEPSS rescore
  64. 2026-06-11 13:58 UTCEPSS rescore
  65. 2026-06-11 13:58 UTCEPSS rescore
  66. 2026-06-10 13:21 UTCEPSS rescore
  67. 2026-06-10 13:21 UTCEPSS rescore
  68. 2026-06-08 14:15 UTCEPSS rescore
  69. 2026-06-08 14:15 UTCEPSS rescore
  70. 2026-06-07 15:23 UTCEPSS rescore
  71. 2026-06-07 15:23 UTCEPSS rescore
  72. 2026-06-06 13:46 UTCEPSS rescore
  73. 2026-06-06 13:46 UTCEPSS rescore
  74. 2026-06-05 22:46 UTCEPSS rescore
  75. 2026-06-05 22:46 UTCEPSS rescore

Related CVEs(same product + same vendor)

Frequently asked(5)

What is CVE-2022-50630?
CVE-2022-50630 is a high vulnerability published on December 8, 2025. In the Linux kernel, the following vulnerability has been resolved: mm: hugetlb: fix UAF in hugetlbhandleuserfault The vmalock and hugetlbfault_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…
When was CVE-2022-50630 disclosed?
CVE-2022-50630 was first published in the National Vulnerability Database on December 8, 2025, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-50630 actively exploited?
CVE-2022-50630 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 95.4% of all scored CVEs.
What is the CVSS score of CVE-2022-50630?
CVE-2022-50630 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2022-50630?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-50630, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2022-50630

Explore →

Is Your Infrastructure Affected by CVE-2022-50630?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs