CVE-2022-50517

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

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, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2025-32038 (ENISA EUVD) · GHSA-8jc8-9g79-v496 (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
3rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 7, 2025

Last Modified

August 5, 2026

References (2)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 6.0.7 (fixes >=5.19.0)—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.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.0.7-1: fixed in 6.0.7-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.0.7-1: fixed in 6.0.7-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.0.7-1: fixed in 6.0.7-1
—

Data Freshness Timeline

(refreshed 7× in last 7d / 38× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 201 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 102 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-06 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  2. 2026-11-05 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  3. 2026-11-04 16:30 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  4. 2026-11-03 16:40 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  5. 2026-11-02 16:39 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  6. 2026-11-01 16:30 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  7. 2026-10-31 16:29 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  8. 2026-10-30 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  9. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  10. 2026-10-28 16:28 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  11. 2026-10-27 16:28 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  12. 2026-10-26 16:28 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  13. 2026-10-25 17:53 UTCEG score recompute
  14. 2026-10-25 16:29 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  15. 2026-10-24 17:40 UTCEG score recompute
  16. 2026-10-24 17:40 UTCGHSA enrichmentGHSA-8jc8-9g79-v496 · GitHub CVSS 5.5
  17. 2026-10-24 16:29 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  18. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  19. 2026-10-22 16:30 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  20. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  21. 2026-10-20 16:29 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  22. 2026-10-19 16:28 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  23. 2026-10-19 11:25 UTCOSV refresh
  24. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  25. 2026-10-18 08:19 UTCEG score recompute
Show 74 more
  1. 2026-10-17 16:29 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  2. 2026-10-16 16:35 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  3. 2026-10-15 16:28 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  4. 2026-10-14 16:29 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  5. 2026-10-13 16:29 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  6. 2026-10-12 18:40 UTCEG score recompute
  7. 2026-10-12 16:30 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  8. 2026-10-11 22:04 UTCEG score recompute
  9. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  10. 2026-10-10 19:57 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  11. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  12. 2026-10-08 17:05 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  13. 2026-10-07 23:45 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  14. 2026-10-06 15:14 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  15. 2026-10-05 17:40 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  16. 2026-10-04 23:19 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  17. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  18. 2026-09-30 16:13 UTCEG score recompute
  19. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  20. 2026-09-27 13:42 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  21. 2026-09-26 19:03 UTCOSV refresh
  22. 2026-09-26 15:55 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  23. 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  24. 2026-09-24 14:00 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  25. 2026-09-23 13:45 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  26. 2026-09-20 20:13 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  27. 2026-09-16 14:05 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  28. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  29. 2026-09-15 03:07 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  30. 2026-09-13 16:44 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  31. 2026-09-11 14:50 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  32. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  33. 2026-09-08 21:57 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  34. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  35. 2026-09-07 04:18 UTCOSV refresh
  36. 2026-09-06 13:45 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  37. 2026-09-05 15:25 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  38. 2026-09-04 13:57 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  39. 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  40. 2026-09-02 14:09 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  41. 2026-09-01 13:51 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  42. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  43. 2026-08-30 01:19 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  44. 2026-08-28 21:38 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  45. 2026-08-27 14:22 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  46. 2026-08-26 14:43 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  47. 2026-08-25 13:46 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  48. 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  49. 2026-08-21 23:46 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  50. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  51. 2026-08-20 14:01 UTCOSV refresh
  52. 2026-08-19 17:01 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  53. 2026-08-17 13:44 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  54. 2026-08-16 14:53 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  55. 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  56. 2026-08-15 01:27 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  57. 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  58. 2026-08-12 13:48 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  59. 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  60. 2026-08-08 16:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  61. 2026-08-07 16:24 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  62. 2026-08-06 13:44 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  63. 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  64. 2026-08-05 09:19 UTCEG score recompute
  65. 2026-08-05 09:19 UTCGHSA enrichmentGHSA-8jc8-9g79-v496 · GitHub CVSS 5.5
  66. 2026-08-04 15:07 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  67. 2026-08-04 10:56 UTCEG score recompute
  68. 2026-08-04 10:56 UTCGHSA enrichmentGHSA-8jc8-9g79-v496 · GitHub CVSS 5.5
  69. 2026-08-04 10:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  70. 2026-08-04 09:29 UTCEG score recompute
  71. 2026-08-04 09:29 UTCGHSA enrichmentGHSA-8jc8-9g79-v496 · GitHub CVSS 5.5
  72. 2026-08-03 10:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  73. 2026-08-02 02:24 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  74. 2026-08-01 04:13 UTCEPSS rescoreEPSS 0.1% · 2nd percentile

Frequently asked(5)

What is CVE-2022-50517?
CVE-2022-50517 is a medium-severity vulnerability; its CVE record was published on October 7, 2025. 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…
When was the CVE record for CVE-2022-50517 published?
The CVE record for CVE-2022-50517 was published on October 7, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 5, 2026; the record at its source may have been updated since.
Is CVE-2022-50517 actively exploited?
CVE-2022-50517 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (3rd percentile of EPSS-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?
A fix for CVE-2022-50517 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.

Book a Demo →Browse All CVEs