CVE-2026-90383

Linux · Kernel

A vulnerability in the Linux kernel SGI GRU driver allows local users to trigger unsafe page table walks, potentially leading to privilege escalation or system instability.

Executive summary

A high-severity vulnerability in the Linux kernel SGI GRU driver allows a local, authenticated attacker to gain escalated privileges or cause a system crash.

Vulnerability

The GRU TLB miss handler performs page table walks without appropriate locking or reference counting, and incorrectly utilizes kernel page table accessors on user page tables. This flaw requires a local attacker with low privileges to trigger the race condition or memory corruption.

Business impact

The exploitation of this kernel-level vulnerability could allow an attacker to bypass security controls, leading to full system compromise. Given the CVSS score of 7.8, this represents a significant risk to the integrity and availability of the host system. Successful exploitation could result in unauthorized data access, system-wide crashes, or the installation of persistent malicious code.

Remediation

Immediate Action: Update the Linux kernel to version 6.12.110, 6.18.52, 7.2.6, or later, depending on your current distribution branch.

Proactive Monitoring: Monitor system logs for kernel-related faults or unexpected crashes that may indicate exploitation attempts.

Compensating Controls: Restrict local shell access to untrusted users and enforce principle of least privilege to minimize the potential for an attacker to reach the vulnerable code path.

Exploitation status

Public Exploit Available: Unknown

Analyst recommendation

This vulnerability presents a high risk to environment security due to its potential for local privilege escalation. Administrators should prioritize patching the Linux kernel across all affected systems. If immediate patching is not feasible, restrict local access to the affected hardware to authorized personnel only to mitigate the attack vector.

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