CVE-2026-45950
Analyzed Analyzed - Analysis Complete
Memory Leak in Linux Kernel StarFive Crypto Driver

Publication date: 2026-05-27

Last updated on: 2026-06-16

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: crypto: starfive - Fix memory leak in starfive_aes_aead_do_one_req() The starfive_aes_aead_do_one_req() function allocates rctx->adata with kzalloc() but fails to free it if sg_copy_to_buffer() or starfive_aes_hw_init() fails, which lead to memory leaks. Since rctx->adata is unconditionally freed after the write_adata operations, ensure consistent cleanup by freeing the allocation in these earlier error paths as well. Compile tested only. Issue found using a prototype static analysis tool and code review.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-27
Last Modified
2026-06-16
Generated
2026-06-16
AI Q&A
2026-05-27
EPSS Evaluated
2026-06-15
NVD
EUVD
Affected Vendors & Products
Showing 3 associated CPEs
Vendor Product Version / Range
linux linux_kernel From 6.13 (inc) to 6.18.14 (exc)
linux linux_kernel From 6.19 (inc) to 6.19.4 (exc)
linux linux_kernel From 6.10 (inc) to 6.12.75 (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
Mitigation Strategies

The vulnerability is a memory leak in the starfive_aes_aead_do_one_req() function of the Linux kernel related to the starfive crypto driver.

To mitigate this vulnerability, update your Linux kernel to a version where this issue has been fixed, as the patch ensures proper cleanup of allocated memory in error paths.

Executive Summary

This vulnerability is a memory leak in the Linux kernel's starfive AES encryption function starfive_aes_aead_do_one_req(). The function allocates memory for rctx->adata using kzalloc(), but if certain operations like sg_copy_to_buffer() or starfive_aes_hw_init() fail, the allocated memory is not freed, causing a memory leak.

The issue arises because the allocated memory is only freed unconditionally after the write_adata operations, but not in the earlier error paths where failures occur. The fix ensures that the allocated memory is freed consistently even when those earlier errors happen.

Impact Analysis

This vulnerability can lead to memory leaks in the Linux kernel when the starfive AES encryption function encounters certain errors. Over time, these memory leaks could cause increased memory usage, potentially degrading system performance or leading to resource exhaustion.

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