The vulnerability in the Linux kernel tracing code arises from improper handling of cached module event filters. When a module-only event filter such as ':mod:foo' is cached before the module 'foo' is loaded, the event_mod->match pointer is NULL. If a later write attempts to remove a specific match from this module, the function remove_cache_mod() passes the NULL pointer to strcmp(), leading to a NULL pointer dereference and kernel crash. The issue was reproducible on x86_64 systems under contention. The patch adds a check for event_mod->match before calling strcmp(), aligning with existing NULL checks for other cached fields. The removal operation still returns -EINVAL for mismatched removals, and broad cached module filters can be removed with the syntax '!:mod:<module>'.

Exploitation of this vulnerability causes a NULL pointer dereference in kernel space, resulting in a kernel crash (BUG). This leads to denial of service by crashing the affected system. There is no indication of privilege escalation or code execution from the provided data.

A fix has been implemented in the Linux kernel to check for NULL pointers before comparison in the tracing module event cache removal code. Users should update to the fixed kernel version once available. Since this is a kernel vulnerability, applying the official kernel patch or upgrading to a kernel version containing this fix is the recommended remediation. Patch status is not explicitly confirmed in the provided data; users should consult the official Linux kernel advisories for the exact fixed versions and apply updates accordingly.