VDB

CVE-2025-40274

CVE-2025-40274 PUBLISHED CVSS 7.8 HIGH

KVM: guest_memfd: Remove bindings on memslot deletion when gmem is dying

Reported by linux · Published December 6, 2025

In the Linux kernel, the following vulnerability has been resolved: KVM: guest_memfd: Remove bindings on memslot deletion when gmem is dying When unbinding a memslot from a guest_memfd instance, remove the bindings even if the guest_memfd file is dying, i.e. even if its file refcount has gone to zero. If the memslot is freed before the file is fully released, nullifying the memslot side of the binding in kvm_gmem_release() will write to freed memory, as detected by syzbot+KASAN: ================================================================== BUG: KASAN: slab-use-after-free in kvm_gmem_release+0x176/0x440 virt/kvm/guest_memfd.c:353 Write of size 8 at addr ffff88807befa508 by task syz.0.17/6022 CPU: 0 UID: 0 PID: 6022 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025 Call Trace: <TASK> dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0xca/0x240 mm/kasan/report.c:482 kasan_report+0x118/0x150 mm/kasan/report.c:595 kvm_gmem_release+0x176/0x440 virt/kvm/guest_memfd.c:353 __fput+0x44c/0xa70 fs/file_table.c:468 task_work_run+0x1d4/0x260 kernel/task_work.c:227 resume_user_mode_work include/linux/resume_user_mode.h:50 [inline] exit_to_user_mode_loop+0xe9/0x130 kernel/entry/common.c:43 exit_to_user_mode_prepare include/linux/irq-entry-common.h:225 [inline] syscall_exit_to_user_mode_work include/linux/entry-common.h:175 [inline] syscall_exit_to_user_mode include/linux/entry-common.h:210 [inline] do_syscall_64+0x2bd/0xfa0 arch/x86/entry/syscall_64.c:100 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fbeeff8efc9 </TASK> Allocated by task 6023: kasan_save_stack mm/kasan/common.c:56 [inline] kasan_save_track+0x3e/0x80 mm/kasan/common.c:77 poison_kmalloc_redzone mm/kasan/common.c:397 [inline] __kasan_kmalloc+0x93/0xb0 mm/kasan/common.c:414 kasan_kmalloc include/linux/kasan.h:262 [inline] __kmalloc_cache_noprof+0x3e2/0x700 mm/slub.c:5758 kmalloc_noprof include/linux/slab.h:957 [inline] kzalloc_noprof include/linux/slab.h:1094 [inline] kvm_set_memory_region+0x747/0xb90 virt/kvm/kvm_main.c:2104 kvm_vm_ioctl_set_memory_region+0x6f/0xd0 virt/kvm/kvm_main.c:2154 kvm_vm_ioctl+0x957/0xc60 virt/kvm/kvm_main.c:5201 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:597 [inline] __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:583 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0xfa0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f Freed by task 6023: kasan_save_stack mm/kasan/common.c:56 [inline] kasan_save_track+0x3e/0x80 mm/kasan/common.c:77 kasan_save_free_info+0x46/0x50 mm/kasan/generic.c:584 poison_slab_object mm/kasan/common.c:252 [inline] __kasan_slab_free+0x5c/0x80 mm/kasan/common.c:284 kasan_slab_free include/linux/kasan.h:234 [inline] slab_free_hook mm/slub.c:2533 [inline] slab_free mm/slub.c:6622 [inline] kfree+0x19a/0x6d0 mm/slub.c:6829 kvm_set_memory_region+0x9c4/0xb90 virt/kvm/kvm_main.c:2130 kvm_vm_ioctl_set_memory_region+0x6f/0xd0 virt/kvm/kvm_main.c:2154 kvm_vm_ioctl+0x957/0xc60 virt/kvm/kvm_main.c:5201 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:597 [inline] __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:583 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0xfa0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f Deliberately don't acquire filemap invalid lock when the file is dying as the lifecycle of f_mapping is outside the purview of KVM. Dereferencing the mapping is *probably* fine, but there's no need to invalidate anything as memslot deletion is responsible for zapping SPTEs, and the only code that can access the dying file is kvm_gmem_release(), whose core code is mutual ---truncated---

EPSS 0.15% · 4.0th percentile

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
python3-perf6.12Amazon Linux1:6.12.63-84.121.amzn2023
kernel6.12-develAmazon Linux1:6.12.63-84.121.amzn2023
kernel6.12-headersAmazon Linux1:6.12.63-84.121.amzn2023
kernel6.12-toolsAmazon Linux1:6.12.63-84.121.amzn2023
kernel6.12-tools-develAmazon Linux1:6.12.63-84.121.amzn2023
kernel-livepatch-6.12.63-84.121Amazon Linux1:1.0-0.amzn2023
perf6.12Amazon Linux1:6.12.63-84.121.amzn2023
kernel6.12-modules-extraAmazon Linux1:6.12.63-84.121.amzn2023
bpftool6.12Amazon Linux1:6.12.63-84.121.amzn2023
kernel6.12Amazon Linux1:6.12.63-84.121.amzn2023
kernel6.12-libbpf-develAmazon Linux1:6.12.63-84.121.amzn2023
linux_kernellinux6.18, 6.17.9, 6.12.59

1 more packages have a fixed version. See every fix in Lookup.

Risk scores

CVSS 3.1
7.8
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score
0.15%
4.0th percentile

Affected products

VendorProductVersions
LinuxLinuxa7800aa80ea4d5356b8474c2302812e9d4926fa6, a7800aa80ea4d5356b8474c2302812e9d4926fa6, a7800aa80ea4d5356b8474c2302812e9d4926fa6
LinuxLinux6.8, 0, 6.12.59
amazon:2023python3-perf6.120
amazon:2023kernel6.12-devel0
linuxlinux_kernel6.8, 6.8, 6.8
amazon:2023kernel6.12-headers0
amazon:2023kernel6.12-tools0
amazon:2023kernel6.12-tools-devel0
amazon:2023kernel-livepatch-6.12.63-84.1210
amazon:2023perf6.120
amazon:2023kernel6.12-modules-extra0
amazon:2023bpftool6.120
amazon:2023kernel6.120
amazon:2023kernel6.12-libbpf-devel0
LinuxLinux6.12.59, *, 0
amazon:2023kernel6.12-modules-extra-common0
amazon:2023kernel6.12-libbpf-static0
amazon:2023kernel6.12-libbpf0

Timeline

  • Dec 6, 2025 CVE Published
  • Dec 7, 2025 EPSS Score (30 in total, the first dated here)
  • Dec 7, 2025 CVE Updated
  • Mar 29, 2026 Distribution Patch (147 in total, the first dated here)
  • Mar 29, 2026 Security Advisory (150 in total, the first dated here)
  • Jun 8, 2026 Coalition ESS Score

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2025-40274
vulnetix vdb fixes CVE-2025-40274

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-40274/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›