CVE-2025-68810

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-01-13. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

KVM: Disallow toggling KVM_MEM_GUEST_MEMFD on an existing memslot

Reject attempts to disable KVM_MEM_GUEST_MEMFD on a memslot that was initially created with a guest_memfd binding, as KVM doesn't support toggling KVM_MEM_GUEST_MEMFD on existing memslots. KVM prevents enabling KVM_MEM_GUEST_MEMFD, but doesn't prevent clearing the flag.

Failure to reject the new memslot results in a use-after-free due to KVM not unbinding from the guest_memfd instance. Unbinding on a FLAGS_ONLY change is easy enough, and can/will be done as a hardening measure (in anticipation of KVM supporting dirty logging on guest_memfd at some point), but fixing the use-after-free would only address the immediate symptom.

================================================================== BUG: KASAN: slab-use-after-free in kvm_gmem_release+0x362/0x400 [kvm] Write of size 8 at addr ffff8881111ae908 by task repro/745

CPU: 7 UID: 1000 PID: 745 Comm: repro Not tainted 6.18.0-rc6-115d5de2eef3-next-kasan #3 NONE Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015 Call Trace: dump_stack_lvl+0x51/0x60 print_report+0xcb/0x5c0 kasan_report+0xb4/0xe0 kvm_gmem_release+0x362/0x400 [kvm] __fput+0x2fa/0x9d0 task_work_run+0x12c/0x200 do_exit+0x6ae/0x2100 do_group_exit+0xa8/0x230 __x64_sys_exit_group+0x3a/0x50 x64_sys_call+0x737/0x740 do_syscall_64+0x5b/0x900 entry_SYSCALL_64_after_hwframe+0x4b/0x53 RIP: 0033:0x7f581f2eac31

Allocated by task 745 on cpu 6 at 9.746971s: kasan_save_stack+0x20/0x40 kasan_save_track+0x13/0x50 __kasan_kmalloc+0x77/0x90 kvm_set_memory_region.part.0+0x652/0x1110 [kvm] kvm_vm_ioctl+0x14b0/0x3290 [kvm] __x64_sys_ioctl+0x129/0x1a0 do_syscall_64+0x5b/0x900 entry_SYSCALL_64_after_hwframe+0x4b/0x53

Freed by task 745 on cpu 6 at 9.747467s: kasan_save_stack+0x20/0x40 kasan_save_track+0x13/0x50 __kasan_save_free_info+0x37/0x50 __kasan_slab_free+0x3b/0x60 kfree+0xf5/0x440 kvm_set_memslot+0x3c2/0x1160 [kvm] kvm_set_memory_region.part.0+0x86a/0x1110 [kvm] kvm_vm_ioctl+0x14b0/0x3290 [kvm] __x64_sys_ioctl+0x129/0x1a0 do_syscall_64+0x5b/0x900 entry_SYSCALL_64_after_hwframe+0x4b/0x53

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

Published

January 13, 2026

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Jul 30, 2026
No patch confirmed yet.
generic

KVM: Disallow toggling KVM_MEM_GUEST_MEMFD on an existing memslot - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/cb51bef465d8ec60a968507330e01020e35dc127
generic

KVM: Disallow toggling KVM_MEM_GUEST_MEMFD on an existing memslot - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9935df5333aa503a18de5071f53762b65c783c4c
generic

KVM: Disallow toggling KVM_MEM_GUEST_MEMFD on an existing memslot - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/89dbbe6ff323fc34659621a577fe0af913f47386

Vendor Advisories for CVE-2025-68810(1)

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

Patch Availability(20)

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 rangeFixed inDependents
linux6.12.38-1 ... 6.12.69-1~bpo12+1 (10 versions)6.12.69-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (93 versions)6.18.3-1

All Vendor Advisories

(20)

Data Freshness Timeline

(refreshed 6× in last 7d / 24× 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 195 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2025-68810?
CVE-2025-68810 is a high vulnerability published on January 13, 2026. In the Linux kernel, the following vulnerability has been resolved: KVM: Disallow toggling KVMMEMGUEST_MEMFD on an existing memslot Reject attempts to disable KVMMEMGUEST_MEMFD on a memslot that was initially created with a guest_memfd binding, as KVM doesn't support toggling KVMMEMGUEST_MEMFD on…
When was CVE-2025-68810 disclosed?
CVE-2025-68810 was first published in the National Vulnerability Database on January 13, 2026, 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-2025-68810 actively exploited?
CVE-2025-68810 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 95.9% of all scored CVEs.
What is the CVSS score of CVE-2025-68810?
CVE-2025-68810 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2025-68810?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-68810, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-68810

Explore →

Is Your Infrastructure Affected by CVE-2025-68810?

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