The Linux kernel tracing subsystem suffered a memory leak caused by improper handling of histogram trigger fields. When a trigger containing a disallowed modifier is created, the kernel builds internal field objects but fails to store and free them correctly. This leaves orphaned kernel memory objects that accumulate with repeated trigger installation attempts. While the issue does not provide remote code execution or privilege escalation, it can lead to kernel memory exhaustion and system instability if exploited repeatedly.

This vulnerability affected all Linux kernel versions that contain the tracing histogram feature before the fix commit e0213434fe3e. No specific affected version range is provided; therefore, any kernel build prior to the application of the patch is potentially impacted.

The CVSS score of 5.5 indicates a moderate severity, while the EPSS score of < 1% suggests a very low probability of exploitation. The vulnerability is not listed in CISA's KEV catalog. The exploit requires the ability to create or modify tracing triggers, which is typically a local privilege operation. This memory leak can lead to kernel memory exhaustion and a denial of service via OOM if repeated many times. Current evidence indicates low likelihood of widespread exploitation, but the risk of system instability increases with repeated use.