CVE-2026-46171
Analyzed Analyzed - Analysis Complete
Memory Leak in Linux Kernel KVM RISC-V

Publication date: 2026-05-28

Last updated on: 2026-06-11

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: riscv: kvm: fix vector context allocation leak When the second kzalloc (host_context.vector.datap) fails in kvm_riscv_vcpu_alloc_vector_context, the first allocation (guest_context.vector.datap) is leaked. Free it before returning.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-28
Last Modified
2026-06-11
Generated
2026-06-17
AI Q&A
2026-05-28
EPSS Evaluated
2026-06-16
NVD
EUVD
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
linux linux_kernel From 6.19 (inc) to 7.0.7 (exc)
linux linux_kernel From 6.5 (inc) to 6.18.30 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-401 The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Impact Analysis

This vulnerability can lead to a memory leak in the Linux kernel when running KVM on RISC-V architectures. Over time, repeated failures in allocation could cause increased memory usage, potentially degrading system performance or stability. However, it does not directly lead to code execution or privilege escalation.

Executive Summary

This vulnerability exists in the Linux kernel's RISC-V KVM (Kernel-based Virtual Machine) implementation. Specifically, it involves a memory allocation leak in the function kvm_riscv_vcpu_alloc_vector_context. When the second memory allocation (kzalloc) for host_context.vector.datap fails, the first allocation for guest_context.vector.datap is not freed, causing a memory leak. The fix involves freeing the first allocation before returning when the second allocation fails.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-46171. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart