CVE-2026-89750

7.8

Linux · Kernel

A use-after-free vulnerability in the Linux kernel tracing/user_events subsystem allows local attackers to cause system instability or potential code execution via a race condition during fork.

Executive summary

A high-severity use-after-free flaw in the Linux kernel tracing subsystem could allow a local authenticated attacker to trigger memory corruption and potential system compromise.

Vulnerability

The vulnerability exists within the user_events tracing component, where a failure in user_event_mm_alloc during fork duplication leaves a stale pointer to the parent process tracing state. An authenticated local attacker can trigger this condition to cause a use-after-free, impacting kernel memory integrity.

Business impact

The vulnerability carries a CVSS score of 7.8, reflecting its potential for full system compromise from a local context. Successful exploitation could lead to privilege escalation, arbitrary code execution within the kernel, or complete system denial of service. Such an impact is severe for environments relying on Linux for critical infrastructure or multi-tenant hosting, where isolation between processes is a primary security requirement.

Remediation

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

Proactive Monitoring: Monitor system logs for kernel panic events or KASAN reports that indicate memory corruption or use-after-free errors.

Compensating Controls: Restrict access to tracing features and limit the ability of unprivileged users to execute complex ioctl calls if patching cannot be performed immediately.

Exploitation status

Public Exploit Available: Unknown

Analyst recommendation

Given the severity of potential kernel-level exploitation, organizations should prioritize patching the Linux kernel to the aforementioned fixed versions. System administrators should verify their current kernel version and apply distribution-specific updates as soon as they become available to eliminate this risk.

More Linux CVEs all →

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief No CVSS score yet; tracked as early warning
  3. Analyst report written
  4. Published in the daily brief high section

Sources