A use-after-free vulnerability in the Linux kernel tracing subsystem permits a local attacker with low privileges to trigger a system panic and potential memory corruption.

The flaw exists in the event history trigger mechanism where duplicate naming of triggers leads to an improper cleanup process. An attacker with local access (PR:L) can manipulate tracefs to create a dangling pointer, which is subsequently dereferenced to cause a kernel panic (A:H) and potential code execution.

Successful exploitation of this vulnerability results in a denial of service through a kernel panic, effectively crashing the host system. Given the CVSS score of 7.8, this represents a significant risk to system availability, particularly in multi-tenant environments where local users might attempt to disrupt services or escalate privileges by exploiting kernel memory state.

Immediate Action: Update the Linux kernel to version 6.12.109, 6.18.50, 7.2.4, or later, as provided by your distribution vendor.

Proactive Monitoring: Monitor system logs for kernel oops or panic messages specifically related to tracefs or hist trigger operations, which may indicate attempted exploitation.

Compensating Controls: Restrict access to the tracefs filesystem (typically mounted at /sys/kernel/tracing) to authorized administrative users only to prevent unprivileged users from interacting with the vulnerable trigger interface.

Public Exploit Available: Unknown.

The severity of this issue is high due to its impact on system stability and potential for kernel-level memory manipulation. Administrators should prioritize patching the Linux kernel across all affected environments. In instances where immediate patching is not possible, strictly enforcing filesystem permissions on the tracing directory is necessary to mitigate the risk of exploitation by low-privileged users.