CVE-2022-50517

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2025-10-07. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

mm/huge_memory: do not clobber swp_entry_t during THP split

The following has been observed when running stressng mmap since commit b653db77350c ("mm: Clear page->private when splitting or migrating a page")

watchdog: BUG: soft lockup - CPU#75 stuck for 26s! [stress-ng:9546] CPU: 75 PID: 9546 Comm: stress-ng Tainted: G E 6.0.0-revert-b653db77-fix+ #29 0357d79b60fb09775f678e4f3f64ef0579ad1374 Hardware name: SGI.COM C2112-4GP3/X10DRT-P-Series, BIOS 2.0a 05/09/2016 RIP: 0010:xas_descend+0x28/0x80 Code: cc cc 0f b6 0e 48 8b 57 08 48 d3 ea 83 e2 3f 89 d0 48 83 c0 04 48 8b 44 c6 08 48 89 77 18 48 89 c1 83 e1 03 48 83 f9 02 75 08 <48> 3d fd 00 00 00 76 08 88 57 12 c3 cc cc cc cc 48 c1 e8 02 89 c2 RSP: 0018:ffffbbf02a2236a8 EFLAGS: 00000246 RAX: ffff9cab7d6a0002 RBX: ffffe04b0af88040 RCX: 0000000000000002 RDX: 0000000000000030 RSI: ffff9cab60509b60 RDI: ffffbbf02a2236c0 RBP: 0000000000000000 R08: ffff9cab60509b60 R09: ffffbbf02a2236c0 R10: 0000000000000001 R11: ffffbbf02a223698 R12: 0000000000000000 R13: ffff9cab4e28da80 R14: 0000000000039c01 R15: ffff9cab4e28da88 FS: 00007fab89b85e40(0000) GS:ffff9cea3fcc0000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fab84e00000 CR3: 00000040b73a4003 CR4: 00000000003706e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: xas_load+0x3a/0x50 __filemap_get_folio+0x80/0x370 ? put_swap_page+0x163/0x360 pagecache_get_page+0x13/0x90 __try_to_reclaim_swap+0x50/0x190 scan_swap_map_slots+0x31e/0x670 get_swap_pages+0x226/0x3c0 folio_alloc_swap+0x1cc/0x240 add_to_swap+0x14/0x70 shrink_page_list+0x968/0xbc0 reclaim_page_list+0x70/0xf0 reclaim_pages+0xdd/0x120 madvise_cold_or_pageout_pte_range+0x814/0xf30 walk_pgd_range+0x637/0xa30 __walk_page_range+0x142/0x170 walk_page_range+0x146/0x170 madvise_pageout+0xb7/0x280 ? asm_common_interrupt+0x22/0x40 madvise_vma_behavior+0x3b7/0xac0 ? find_vma+0x4a/0x70 ? find_vma+0x64/0x70 ? madvise_vma_anon_name+0x40/0x40 madvise_walk_vmas+0xa6/0x130 do_madvise+0x2f4/0x360 __x64_sys_madvise+0x26/0x30 do_syscall_64+0x5b/0x80 ? do_syscall_64+0x67/0x80 ? syscall_exit_to_user_mode+0x17/0x40 ? do_syscall_64+0x67/0x80 ? syscall_exit_to_user_mode+0x17/0x40 ? do_syscall_64+0x67/0x80 ? do_syscall_64+0x67/0x80 ? common_interrupt+0x8b/0xa0 entry_SYSCALL_64_after_hwframe+0x63/0xcd

The problem can be reproduced with the mmtests config config-workload-stressng-mmap. It does not always happen and when it triggers is variable but it has happened on multiple machines.

The intent of commit b653db77350c patch was to avoid the case where PG_private is clear but folio->private is not-NULL. However, THP tail pages uses page->private for "swp_entry_t if folio_test_swapcache()" as stated in the documentation for struct folio. This patch only clobbers page->private for tail pages if the head page was not in swapcache and warns once if page->private had an unexpected value.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

October 7, 2025

Last Modified

August 5, 2026

References (2)

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.0.7—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 14× 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 114 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:56 UTCGHSA enrichment
  7. 2026-08-04 10:35 UTCEPSS rescore
  8. 2026-08-04 09:29 UTCEG score recompute
  9. 2026-08-04 09:29 UTCGHSA enrichment
  10. 2026-08-03 10:33 UTCEPSS rescore
  11. 2026-08-02 02:24 UTCEPSS rescore
  12. 2026-08-01 04:13 UTCEPSS rescore
  13. 2026-08-01 04:13 UTCEPSS rescore
  14. 2026-07-30 16:25 UTCEPSS rescore
  15. 2026-07-30 01:28 UTCEPSS rescore
  16. 2026-07-28 15:34 UTCEPSS rescore
  17. 2026-07-26 14:52 UTCEPSS rescore
  18. 2026-07-26 14:52 UTCEPSS rescore
  19. 2026-07-25 14:16 UTCEPSS rescore
  20. 2026-07-24 14:15 UTCEPSS rescore
  21. 2026-07-23 18:11 UTCOSV refresh
  22. 2026-07-23 14:16 UTCEPSS rescore
  23. 2026-07-23 14:16 UTCEPSS rescore
  24. 2026-07-23 02:17 UTCEG score recompute
  25. 2026-07-22 23:04 UTCEG score recompute
Show 75 more
  1. 2026-07-22 14:06 UTCEPSS rescore
  2. 2026-07-22 14:06 UTCEPSS rescore
  3. 2026-07-21 15:23 UTCEPSS rescore
  4. 2026-07-21 15:23 UTCEPSS rescore
  5. 2026-07-20 17:05 UTCEPSS rescore
  6. 2026-07-19 14:29 UTCEPSS rescore
  7. 2026-07-19 14:29 UTCEPSS rescore
  8. 2026-07-19 02:27 UTCEPSS rescore
  9. 2026-07-19 02:27 UTCEPSS rescore
  10. 2026-07-18 10:03 UTCEPSS rescore
  11. 2026-07-18 10:03 UTCEPSS rescore
  12. 2026-07-16 17:00 UTCEPSS rescore
  13. 2026-07-15 16:56 UTCEPSS rescore
  14. 2026-07-15 16:56 UTCEPSS rescore
  15. 2026-07-15 01:58 UTCEPSS rescore
  16. 2026-07-15 01:58 UTCEPSS rescore
  17. 2026-07-13 22:28 UTCEPSS rescore
  18. 2026-07-13 22:28 UTCEPSS rescore
  19. 2026-07-13 06:11 UTCEPSS rescore
  20. 2026-07-13 06:11 UTCEPSS rescore
  21. 2026-07-12 05:44 UTCEPSS rescore
  22. 2026-07-11 08:25 UTCEPSS rescore
  23. 2026-07-11 08:25 UTCEPSS rescore
  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 16:25 UTCEPSS rescore
  28. 2026-07-06 12:41 UTCOSV refresh
  29. 2026-07-06 02:21 UTCEPSS rescore
  30. 2026-07-04 06:29 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 01:58 UTCEPSS rescore
  49. 2026-06-21 01:58 UTCEPSS rescore
  50. 2026-06-19 19:24 UTCEPSS rescore
  51. 2026-06-19 19:24 UTCEPSS rescore
  52. 2026-06-18 17:51 UTCEPSS rescore
  53. 2026-06-18 17:51 UTCEPSS rescore
  54. 2026-06-18 00:43 UTCOSV refresh
  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

Frequently asked(5)

What is CVE-2022-50517?
CVE-2022-50517 is a medium vulnerability published on October 7, 2025. In the Linux kernel, the following vulnerability has been resolved: mm/hugememory: do not clobber swpentry_t during THP split The following has been observed when running stressng mmap since commit b653db77350c ("mm: Clear page->private when splitting or migrating a page") watchdog: BUG: soft…
When was CVE-2022-50517 disclosed?
CVE-2022-50517 was first published in the National Vulnerability Database on October 7, 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-50517 actively exploited?
CVE-2022-50517 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 96.6% of all scored CVEs.
What is the CVSS score of CVE-2022-50517?
CVE-2022-50517 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2022-50517?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-50517, 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-50517

Explore →

Is Your Infrastructure Affected by CVE-2022-50517?

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

Start Free Scan →Browse All CVEs