CVE-2026-89520

Linux · Kernel

A race condition in the Linux kernel core scheduling mechanism can lead to improper lock handling during task selection, potentially resulting in memory corruption or system instability.

Executive summary

A high-severity race condition in the Linux kernel core scheduling subsystem allows a local authenticated attacker to potentially trigger memory corruption or system crashes.

Vulnerability

The flaw resides in the pick_next_task function, where improper synchronization of sibling runqueue locks allows __sched_core_flip to execute mid-selection. This vulnerability requires local access with low privileges to trigger, as indicated by the CVSS attack vector (AV:L, PR:L).

Business impact

Successful exploitation of this vulnerability can lead to kernel-level memory corruption, which may result in unauthorized data access or a complete denial-of-service condition through system panic. Given the CVSS score of 7.8, this flaw represents a significant risk to the integrity and availability of production systems, particularly those utilizing core scheduling to isolate workloads.

Remediation

Immediate Action: Update the Linux kernel to version 6.18.51, 7.2.4, or later versions where the fix has been backported.

Proactive Monitoring: Monitor system logs for unexpected kernel oops, segmentation faults, or recurring system crashes that may indicate exploitation attempts.

Compensating Controls: Ensure that access to local shell environments is strictly restricted to authorized users, as the vulnerability requires local access to the system to exploit.

Exploitation status

Public Exploit Available: Unknown.

Analyst recommendation

This vulnerability presents a high risk to system stability and security due to its location within the core kernel scheduling logic. System administrators should prioritize testing and deploying the provided kernel updates across all affected environments to eliminate the race condition and ensure continued system integrity.

More Linux CVEs all →

History

CVE Brief tracked this CVE 1 day before it had a CVSS score.

  1. Disclosed CVE record published
  2. Collected by CVE Brief No CVSS score yet; tracked as early warning
  3. CVSS score assigned 7.8 (3.1)
  4. Analyst report written

Sources