CVE-2025-39776

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-09-11. NVD baseline CVSS 7.8; sources differ by 0.0.

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

Also known asEUVD-2025-28936 (ENISA EUVD) · GHSA-84v6-6vmq-3v62 (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

mm/debug_vm_pgtable: clear page table entries at destroy_args()

The mm/debug_vm_pagetable test allocates manually page table entries for the tests it runs, using also its manually allocated mm_struct. That in itself is ok, but when it exits, at destroy_args() it fails to clear those entries with the *_clear functions.

The problem is that leaves stale entries. If another process allocates an mm_struct with a pgd at the same address, it may end up running into the stale entry. This is happening in practice on a debug kernel with CONFIG_DEBUG_VM_PGTABLE=y, for example this is the output with some extra debugging I added (it prints a warning trace if pgtables_bytes goes negative, in addition to the warning at check_mm() function):

[ 2.539353] debug_vm_pgtable: [get_random_vaddr ]: random_vaddr is 0x7ea247140000 [ 2.539366] kmem_cache info [ 2.539374] kmem_cachep 0x000000002ce82385 - freelist 0x0000000000000000 - offset 0x508 [ 2.539447] debug_vm_pgtable: [init_args ]: args->mm is 0x000000002267cc9e (...) [ 2.552800] WARNING: CPU: 5 PID: 116 at include/linux/mm.h:2841 free_pud_range+0x8bc/0x8d0 [ 2.552816] Modules linked in: [ 2.552843] CPU: 5 UID: 0 PID: 116 Comm: modprobe Not tainted 6.12.0-105.debug_vm2.el10.ppc64le+debug #1 VOLUNTARY [ 2.552859] Hardware name: IBM,9009-41A POWER9 (architected) 0x4e0202 0xf000005 of:IBM,FW910.00 (VL910_062) hv:phyp pSeries [ 2.552872] NIP: c0000000007eef3c LR: c0000000007eef30 CTR: c0000000003d8c90 [ 2.552885] REGS: c0000000622e73b0 TRAP: 0700 Not tainted (6.12.0-105.debug_vm2.el10.ppc64le+debug) [ 2.552899] MSR: 800000000282b033 CR: 24002822 XER: 0000000a [ 2.552954] CFAR: c0000000008f03f0 IRQMASK: 0 [ 2.552954] GPR00: c0000000007eef30 c0000000622e7650 c000000002b1ac00 0000000000000001 [ 2.552954] GPR04: 0000000000000008 0000000000000000 c0000000007eef30 ffffffffffffffff [ 2.552954] GPR08: 00000000ffff00f5 0000000000000001 0000000000000048 0000000000004000 [ 2.552954] GPR12: 00000003fa440000 c000000017ffa300 c0000000051d9f80 ffffffffffffffdb [ 2.552954] GPR16: 0000000000000000 0000000000000008 000000000000000a 60000000000000e0 [ 2.552954] GPR20: 4080000000000000 c0000000113af038 00007fffcf130000 0000700000000000 [ 2.552954] GPR24: c000000062a6a000 0000000000000001 8000000062a68000 0000000000000001 [ 2.552954] GPR28: 000000000000000a c000000062ebc600 0000000000002000 c000000062ebc760 [ 2.553170] NIP [c0000000007eef3c] free_pud_range+0x8bc/0x8d0 [ 2.553185] LR [c0000000007eef30] free_pud_range+0x8b0/0x8d0 [ 2.553199] Call Trace: [ 2.553207] [c0000000622e7650] [c0000000007eef30] free_pud_range+0x8b0/0x8d0 (unreliable) [ 2.553229] [c0000000622e7750] [c0000000007f40b4] free_pgd_range+0x284/0x3b0 [ 2.553248] [c0000000622e7800] [c0000000007f4630] free_pgtables+0x450/0x570 [ 2.553274] [c0000000622e78e0] [c0000000008161c0] exit_mmap+0x250/0x650 [ 2.553292] [c0000000622e7a30] [c0000000001b95b8] __mmput+0x98/0x290 [ 2.558344] [c0000000622e7a80] [c0000000001d1018] exit_mm+0x118/0x1b0 [ 2.558361] [c0000000622e7ac0] [c0000000001d141c] do_exit+0x2ec/0x870 [ 2.558376] [c0000000622e7b60] [c0000000001d1ca8] do_group_exit+0x88/0x150 [ 2.558391] [c0000000622e7bb0] [c0000000001d1db8] sys_exit_group+0x48/0x50 [ 2.558407] [c0000000622e7be0] [c00000000003d810] system_call_exception+0x1e0/0x4c0 [ 2.558423] [c0000000622e7e50] [c00000000000d05c] system_call_vectored_common+0x15c/0x2ec (...) [ 2.558892] ---[ end trace 0000000000000000 ]--- [ 2.559022] BUG: Bad rss-counter state mm:000000002267cc9e type:MM_ANONPAGES val:1 [ 2.559037] BUG: non-zero pgtables_bytes on freeing mm: -6144

Here the modprobe process ended up with an allocated mm_struct from the mm_struct slab that was used before by the debug_vm_pgtable test. That is not a problem, since the mm_stru ---truncated---

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/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)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 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 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
4th
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 (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-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-27). 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

September 11, 2025

Last Modified

October 19, 2026

Advisory Details (8)

Auto-updated Jul 31, 2026
Patch available.
Web page

SSA-032379

https://cert-portal.siemens.com/productcert/html/ssa-032379.html
Web pageMentions a patch (unverified)

[SECURITY] [DLA 4328-1] linux-6.1 security update

https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html
Web page

mm/debug_vm_pgtable: clear page table entries at destroy_args() - kernel/git/stable/linux.git - Linux kernel stable tree

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

mm/debug_vm_pgtable: clear page table entries at destroy_args() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7bf57a0709cd7c9088cea8de023d6f4fbf2518b0
Web page

mm/debug_vm_pgtable: clear page table entries at destroy_args() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/63962ff932ef359925b94be2a88df6b4fd4fed0a
Web page

mm/debug_vm_pgtable: clear page table entries at destroy_args() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/61a9f2e5c49f05e3ea2c16674540a075a1b4be6f
Web page

mm/debug_vm_pgtable: clear page table entries at destroy_args() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/561171db3b3eb759ba3f284dba7a76f4476ade03
Web page

mm/debug_vm_pgtable: clear page table entries at destroy_args() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/47d2a149611b8a94d24add9868c442a4af278658

Vendor Advisories for CVE-2025-39776(1)

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

Patch Availability(26)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-fips-6.8 (6.8.0-100.100+fips1) @ noble2026-10-27ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1043.44) @ noble2026-10-27ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1047.50+fips1) @ noble2026-10-27ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-100.100~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1046.52+fips1) @ noble2026-10-27ubuntu
ubuntulinux-tools-gke-64k-6.8 (6.8.0-1043.48) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1046.52) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1051.57~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-kvm-5.15 (5.15.0.1089.85) @ jammy2026-10-27ubuntu
ubuntulinux-tools-gcp-fips-5.15 (5.15.0.1097.87) @ jammy2026-10-27ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-100.100.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1101.99) @ jammy2026-10-27ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1091.89) @ jammy2026-10-27ubuntu
ubuntulinux-tools-realtime-hwe-22.04 (6.8.1-1041.42~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1047.50~22.04.2) @ jammy2026-10-27ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1041.42) @ noble2026-10-27ubuntu
ubuntulinux-tools-ibm-lts-24.04 (6.8.0-1044.44) @ noble2026-10-27ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1023.24) @ noble2026-10-27ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1046.49.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1101.86) @ jammy2026-10-27ubuntu
ubuntulinux-tools-realtime-5.15 (5.15.0.1096.100) @ jammy2026-10-27ubuntu
ubuntulinux-tools-gkeop-5.15 (5.15.0.1080.79) @ jammy2026-10-27ubuntu
ubuntulinux-virtual-6.8 (6.8.0-100.100) @ noble2026-10-27ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1061 (5.15.0-1061.65) @ jammy2026-10-27ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1102.111~20.04.1) @ focal2026-10-27ubuntu
linuxKernel @ 5.15.190 (fixes >=5.15.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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux-6.16.1.106-3~deb11u1 ... 6.1.148-1~deb11u1 (11 versions)
  • every version up to 6.1.153-1~deb11u1: fixed in 6.1.153-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (43 versions)
  • every version up to 6.1.153-1: fixed in 6.1.153-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1, 6.12.41-1, 6.12.43-1, 6.12.43-1~bpo12+1
  • every version up to 6.12.48-1: fixed in 6.12.48-1
—
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
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(24)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

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

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-39776?
CVE-2025-39776 is a high-severity vulnerability; its CVE record was published on September 11, 2025. In the Linux kernel, the following vulnerability has been resolved: mm/debug_vm_pgtable: clear page table entries at destroy_args() The mm/debug_vm_pagetable test allocates manually page table entries for the tests it runs, using also its manually allocated mm_struct. That in itself is ok, but when…
When was the CVE record for CVE-2025-39776 published?
The CVE record for CVE-2025-39776 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 October 19, 2026; the record at its source may have been updated since.
Is CVE-2025-39776 actively exploited?
CVE-2025-39776 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-39776?
CVE-2025-39776 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2025-39776?
A fix for CVE-2025-39776 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-39776 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-39776

Explore →

Is Your Infrastructure Affected by CVE-2025-39776?

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

Book a Demo →Browse All CVEs