When an uprobes probe is unregistered on an x86 Linux kernel, the kernel incorrectly uses the tracer process’s memory layout structure (mm_struct) to locate the virtual memory area. This mismatch can cause the kernel to resolve an address in the wrong process context, potentially leading to unintended kernel memory accesses or corrupted cleanup logic. The result is a possibility of kernel memory corruption, instability, or privilege escalation if the corrupted memory influences control flow or security checks.

All x86 Linux kernel builds that enable uprobes, regardless of specific version, because the issue exists in the unregistration path of the uprobes subsystem. Administrators should verify whether their deployments compile with uprobes support and consider whether any custom kernel modules or patches might expose the flaw.

The CVSS score of 7.8 denotes high severity, while the EPSS score of <1% indicates a low likelihood of active exploitation at present. The vulnerability is not listed in the CISA KEV catalog. Exploitation would likely require local or elevated privileges to trigger the unregistration sequence, such as an attacker who can activate or manipulate an uprobes probe. If successful, the improper memory context could lead to kernel panic or privilege escalation, but no public exploits have been documented.