CVE-2026-90325

Linux · Kernel

A race condition in the Linux kernel block cgroup subsystem leads to a use-after-free vulnerability during IO scheduler switching, potentially allowing local privilege escalation.

Executive summary

A race condition vulnerability in the Linux kernel block cgroup subsystem may allow a local attacker to trigger a use-after-free, resulting in system instability or potential privilege escalation.

Vulnerability

This flaw involves a race condition between the blkcg_activate_policy function and concurrent cgroup deletion, which fails to properly validate the state of the block cgroup (blkg) before acquiring a reference. An authenticated local attacker with low privileges can exploit this race to trigger a use-after-free condition in the kernel.

Business impact

Successful exploitation of this vulnerability allows an attacker to achieve code execution or cause a kernel panic, leading to system downtime. Given the CVSS score of 7.8, this represents a high-severity risk to system integrity and availability, particularly in multi-tenant environments or shared server infrastructures where local access is provided to users.

Remediation

Immediate Action: Update the Linux kernel to version 6.1.17, 6.2.4, 6.6.157, 6.12.110, or later, depending on your distribution's stable branch.

Proactive Monitoring: Monitor kernel logs (dmesg) for signs of memory corruption, segmentation faults, or unexpected kernel panics, which may indicate attempted exploitation.

Compensating Controls: Restrict local access to the system to trusted users only, as the vulnerability requires local access to the affected hardware/software interface to trigger the race condition.

Exploitation status

Public Exploit Available: No

Analyst recommendation

This vulnerability highlights the ongoing risks associated with complex kernel resource management. Administrators should prioritize patching the Linux kernel across all affected production environments to eliminate the potential for local privilege escalation. Given the nature of kernel-level vulnerabilities, a system reboot will be required to finalize the application of the security fix.

More Linux CVEs all →

History

CVE Brief tracked this CVE 3 days 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