Linux Kernel Tracing Instance Error Log Memory Leak Vulnerability

A memory leak vulnerability has been identified in the Linux kernel's tracing subsystem. When a tracing instance is removed, the associated error messages are not properly freed, leading to a memory leak. This issue can be observed by creating a tracing instance, triggering an error, and then removing the instance without releasing the error log. The memory leak can be confirmed using the kernel's memory leak detection feature, which will report the unreferenced objects that were not properly freed.

Impact

Exploitation of this vulnerability leads to a memory leak, where error logs from removed tracing instances are not freed, causing unnecessary memory consumption.

Reproduction

To reproduce this vulnerability, create a tracing instance and introduce an error by writing a specific command that triggers a fault. Afterward, remove the instance but do not clear the error log. Finally, use the kernel's memory leak detection tool to identify the unfreed error log, which indicates the presence of the memory leak.

Remediation

The vulnerability has been addressed in the Linux kernel. Users should upgrade to the latest version where this issue has been fixed.