CVE-2022-49760

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-03-27. 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-2022-55163 (ENISA EUVD) · GHSA-jwgp-qffh-vpgp (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.2%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/hugetlb: fix PTE marker handling in hugetlb_change_protection()

Patch series "mm/hugetlb: uffd-wp fixes for hugetlb_change_protection()".

Playing with virtio-mem and background snapshots (using uffd-wp) on hugetlb in QEMU, I managed to trigger a VM_BUG_ON(). Looking into the details, hugetlb_change_protection() seems to not handle uffd-wp correctly in all cases.

Patch #1 fixes my test case. I don't have reproducers for patch #2, as it requires running into migration entries.

I did not yet check in detail yet if !hugetlb code requires similar care.

This patch (of 2):

There are two problematic cases when stumbling over a PTE marker in hugetlb_change_protection():

(1) We protect an uffd-wp PTE marker a second time using uffd-wp: we will end up in the "!huge_pte_none(pte)" case and mess up the PTE marker.

(2) We unprotect a uffd-wp PTE marker: we will similarly end up in the "!huge_pte_none(pte)" case even though we cleared the PTE, because the "pte" variable is stale. We'll mess up the PTE marker.

For example, if we later stumble over such a "wrongly modified" PTE marker, we'll treat it like a present PTE that maps some garbage page.

This can, for example, be triggered by mapping a memfd backed by huge pages, registering uffd-wp, uffd-wp'ing an unmapped page and (a) uffd-wp'ing it a second time; or (b) uffd-unprotecting it; or (c) unregistering uffd-wp. Then, ff we trigger fallocate(FALLOC_FL_PUNCH_HOLE) on that file range, we will run into a VM_BUG_ON:

[ 195.039560] page:00000000ba1f2987 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x0 [ 195.039565] flags: 0x7ffffc0001000(reserved|node=0|zone=0|lastcpupid=0x1fffff) [ 195.039568] raw: 0007ffffc0001000 ffffe742c0000008 ffffe742c0000008 0000000000000000 [ 195.039569] raw: 0000000000000000 0000000000000000 00000001ffffffff 0000000000000000 [ 195.039569] page dumped because: VM_BUG_ON_PAGE(compound && !PageHead(page)) [ 195.039573] ------------[ cut here ]------------ [ 195.039574] kernel BUG at mm/rmap.c:1346! [ 195.039579] invalid opcode: 0000 [#1] PREEMPT SMP NOPTI [ 195.039581] CPU: 7 PID: 4777 Comm: qemu-system-x86 Not tainted 6.0.12-200.fc36.x86_64 #1 [ 195.039583] Hardware name: LENOVO 20WNS1F81N/20WNS1F81N, BIOS N35ET50W (1.50 ) 09/15/2022 [ 195.039584] RIP: 0010:page_remove_rmap+0x45b/0x550 [ 195.039588] Code: [...] [ 195.039589] RSP: 0018:ffffbc03c3633ba8 EFLAGS: 00010292 [ 195.039591] RAX: 0000000000000040 RBX: ffffe742c0000000 RCX: 0000000000000000 [ 195.039592] RDX: 0000000000000002 RSI: ffffffff8e7aac1a RDI: 00000000ffffffff [ 195.039592] RBP: 0000000000000001 R08: 0000000000000000 R09: ffffbc03c3633a08 [ 195.039593] R10: 0000000000000003 R11: ffffffff8f146328 R12: ffff9b04c42754b0 [ 195.039594] R13: ffffffff8fcc6328 R14: ffffbc03c3633c80 R15: ffff9b0484ab9100 [ 195.039595] FS: 00007fc7aaf68640(0000) GS:ffff9b0bbf7c0000(0000) knlGS:0000000000000000 [ 195.039596] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 195.039597] CR2: 000055d402c49110 CR3: 0000000159392003 CR4: 0000000000772ee0 [ 195.039598] PKRU: 55555554 [ 195.039599] Call Trace: [ 195.039600] [ 195.039602] __unmap_hugepage_range+0x33b/0x7d0 [ 195.039605] unmap_hugepage_range+0x55/0x70 [ 195.039608] hugetlb_vmdelete_list+0x77/0xa0 [ 195.039611] hugetlbfs_fallocate+0x410/0x550 [ 195.039612] ? _raw_spin_unlock_irqrestore+0x23/0x40 [ 195.039616] vfs_fallocate+0x12e/0x360 [ 195.039618] __x64_sys_fallocate+0x40/0x70 [ 195.039620] do_syscall_64+0x58/0x80 [ 195.039623] ? syscall_exit_to_user_mode+0x17/0x40 [ 195.039624] ? do_syscall_64+0x67/0x80 [ 195.039626] entry_SYSCALL_64_after_hwframe+0x63/0xcd [ 195.039628] RIP: 0033:0x7fc7b590651f [ 195.039653] Code: [...] [ 195.039654] RSP: 002b:00007fc7aaf66e70 EFLAGS: 00000293 ORIG_RAX: 000000000000011d [ 195.039655] RAX: ffffffffffffffda RBX: 0000558ef4b7f370 RCX: 00007fc7b590651f ---truncated---

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.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (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.2%
EPSS %ILE
6th
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.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). 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 (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (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 Vulnrichment) · Technical impact total (CISA Vulnrichment). 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

March 27, 2025

Last Modified

October 15, 2026

Advisory Details (2)

Auto-updated Oct 15, 2026
Patch available.
Web page

mm/hugetlb: fix PTE marker handling in hugetlb_change_protection() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6062c992e912df1eedad52cf64efb3d48e8d35c5
Web page

mm/hugetlb: fix PTE marker handling in hugetlb_change_protection() - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2022-49760(1)

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 / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:5.14.0-362.8.1.el9_32023-11-07redhat
linuxKernel @ 6.1.8 (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.1.8-1: fixed in 6.1.8-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.8-1: fixed in 6.1.8-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.8-1: fixed in 6.1.8-1
—

Data Freshness Timeline

(refreshed 8× in last 7d / 37× 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 98 of 190 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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 92 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2022-49760?
CVE-2022-49760 is a medium-severity vulnerability; its CVE record was published on March 27, 2025. In the Linux kernel, the following vulnerability has been resolved: mm/hugetlb: fix PTE marker handling in hugetlb_change_protection() Patch series "mm/hugetlb: uffd-wp fixes for hugetlb_change_protection()". Playing with virtio-mem and background snapshots (using uffd-wp) on hugetlb in QEMU, I…
When was the CVE record for CVE-2022-49760 published?
The CVE record for CVE-2022-49760 was published on March 27, 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 October 15, 2026; the record at its source may have been updated since.
Is CVE-2022-49760 actively exploited?
CVE-2022-49760 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-49760?
CVE-2022-49760 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2022-49760?
A fix for CVE-2022-49760 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-49760 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-49760

Explore →

Is Your Infrastructure Affected by CVE-2022-49760?

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

Book a Demo →Browse All CVEs