Linux kernel
cpe:2.3:a:linux:linux_kernel:*:*:*:*:*:*:*, +4 more
A key reference count leak vulnerability has been identified in the Linux kernel's Rxrpc implementation. When a client call is created, a reference to the key is obtained but not properly released, leading to a memory leak when the call is destroyed. This issue has been addressed by modifying the call destruction process to include the necessary cleanup of the key reference. The vulnerability was present in the Linux kernel stable tree.
The vulnerability could lead to a memory leak by not properly releasing key references, potentially causing increased memory usage over time.
The vulnerability can be reproduced by creating a client call in the Rxrpc layer, which will automatically increment the key reference count. After the call is destroyed, the reference count remains elevated, indicating that the key reference was not properly released. This can be verified by checking the key reference count in the /proc/keys file before and after the call is destroyed.
Users can upgrade to the latest version of the Linux kernel stable tree, where this vulnerability has been fixed.
Our algorithm analyzes dozens of metrics to generate these 8 key vulnerability categories, which are then combined to calculate the overall risk score.