CVE-2025-39775

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 (severity: MODERATE) published 2025-09-11. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2025-28937 (ENISA EUVD) · GHSA-mj2f-v2cm-g63m (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/mremap: fix WARN with uffd that has remap events disabled

Registering userfaultd on a VMA that spans at least one PMD and then mremap()'ing that VMA can trigger a WARN when recovering from a failed page table move due to a page table allocation error.

The code ends up doing the right thing (recurse, avoiding moving actual page tables), but triggering that WARN is unpleasant:

WARNING: CPU: 2 PID: 6133 at mm/mremap.c:357 move_normal_pmd mm/mremap.c:357 [inline] WARNING: CPU: 2 PID: 6133 at mm/mremap.c:357 move_pgt_entry mm/mremap.c:595 [inline] WARNING: CPU: 2 PID: 6133 at mm/mremap.c:357 move_page_tables+0x3832/0x44a0 mm/mremap.c:852 Modules linked in: CPU: 2 UID: 0 PID: 6133 Comm: syz.0.19 Not tainted 6.17.0-rc1-syzkaller-00004-g53e760d89498 #0 PREEMPT(full) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 RIP: 0010:move_normal_pmd mm/mremap.c:357 [inline] RIP: 0010:move_pgt_entry mm/mremap.c:595 [inline] RIP: 0010:move_page_tables+0x3832/0x44a0 mm/mremap.c:852 Code: ... RSP: 0018:ffffc900037a76d8 EFLAGS: 00010293 RAX: 0000000000000000 RBX: 0000000032930007 RCX: ffffffff820c6645 RDX: ffff88802e56a440 RSI: ffffffff820c7201 RDI: 0000000000000007 RBP: ffff888037728fc0 R08: 0000000000000007 R09: 0000000000000000 R10: 0000000032930007 R11: 0000000000000000 R12: 0000000000000000 R13: ffffc900037a79a8 R14: 0000000000000001 R15: dffffc0000000000 FS: 000055556316a500(0000) GS:ffff8880d68bc000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000001b30863fff CR3: 0000000050171000 CR4: 0000000000352ef0 Call Trace: copy_vma_and_data+0x468/0x790 mm/mremap.c:1215 move_vma+0x548/0x1780 mm/mremap.c:1282 mremap_to+0x1b7/0x450 mm/mremap.c:1406 do_mremap+0xfad/0x1f80 mm/mremap.c:1921 __do_sys_mremap+0x119/0x170 mm/mremap.c:1977 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xcd/0x4c0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f00d0b8ebe9 Code: ... RSP: 002b:00007ffe5ea5ee98 EFLAGS: 00000246 ORIG_RAX: 0000000000000019 RAX: ffffffffffffffda RBX: 00007f00d0db5fa0 RCX: 00007f00d0b8ebe9 RDX: 0000000000400000 RSI: 0000000000c00000 RDI: 0000200000000000 RBP: 00007ffe5ea5eef0 R08: 0000200000c00000 R09: 0000000000000000 R10: 0000000000000003 R11: 0000000000000246 R12: 0000000000000002 R13: 00007f00d0db5fa0 R14: 00007f00d0db5fa0 R15: 0000000000000005

The underlying issue is that we recurse during the original page table move, but not during the recovery move.

Fix it by checking for both VMAs and performing the check before the pmd_none() sanity check.

Add a new helper where we perform+document that check for the PMD and PUD level.

Thanks to Harry for bisecting.

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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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
8th
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-11-05). 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 every mission impact level.CISA BOD 26-04: 60 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 every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 partial (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

September 11, 2025

Last Modified

November 5, 2026

Advisory Details (3)

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

mm/mremap: fix WARN with uffd that has remap events disabled - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d70ca21f7bff162a5afae1ddd6f4107adf05ae23
Web page

mm/mremap: fix WARN with uffd that has remap events disabled - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/772e5b4a5e8360743645b9a466842d16092c4f94
Web page

mm/mremap: fix WARN with uffd that has remap events disabled - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1c15b4cd3a97aea013bdb18d9a55ca0384fbb8d4

Vendor Advisories for CVE-2025-39775(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
linuxKernel @ 6.16.4 (fixes >=6.13.0)—osv
linuxKernel @ 6.12.114 (fixes >=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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (174 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.16~rc7-1~exp1 (63 versions)
  • every version up to 6.16.5-1: fixed in 6.16.5-1
—

Data Freshness Timeline

(refreshed 9× in last 7d / 46× 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 193 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 95 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2025-39775?
CVE-2025-39775 is a medium-severity vulnerability; its CVE record was published on September 11, 2025. In the Linux kernel, the following vulnerability has been resolved: mm/mremap: fix WARN with uffd that has remap events disabled Registering userfaultd on a VMA that spans at least one PMD and then mremap()'ing that VMA can trigger a WARN when recovering from a failed page table move due to a page…
When was the CVE record for CVE-2025-39775 published?
The CVE record for CVE-2025-39775 was published on September 11, 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 November 5, 2026; the record at its source may have been updated since.
Is CVE-2025-39775 actively exploited?
CVE-2025-39775 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-39775?
CVE-2025-39775 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-39775?
A fix for CVE-2025-39775 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-39775 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-2025-39775

Explore →

Is Your Infrastructure Affected by CVE-2025-39775?

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

Book a Demo →Browse All CVEs