CVE-2026-46171
Received Received - Intake
Memory Leak in Linux Kernel KVM RISC-V

Publication date: 2026-05-28

Last updated on: 2026-05-28

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-05-28
Generated
2026-05-28
AI Q&A
2026-05-28
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability impact me? :

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.


Can you explain this vulnerability to me?

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.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart