CVE-2026-90217

Linux · Kernel

A state pruning flaw in the Linux kernel BPF iterator allows for potential memory safety violations due to improper comparison of iterator stack slot types.

Executive summary

A high-severity memory management vulnerability in the Linux kernel BPF subsystem could allow a local authenticated attacker to achieve elevated privileges or system compromise.

Vulnerability

The Linux kernel BPF verifier fails to correctly distinguish between MEM_RCU and PTR_UNTRUSTED iterator stack slots during state pruning. This flaw allows a local user with low privileges to bypass safety checks, potentially leading to unauthorized memory access or arbitrary code execution.

Business impact

Successful exploitation of this vulnerability permits a local attacker to escalate privileges, compromise data integrity, or cause a system crash. Given the CVSS score of 7.8, this flaw represents a significant risk to server stability and security, particularly in environments that allow unprivileged users to execute eBPF programs. The ability to manipulate kernel-level memory states poses a critical threat to the overall security posture of the host operating system.

Remediation

Immediate Action: Apply the vendor-provided kernel patch by updating the Linux kernel to version 7.2.6 or later.

Proactive Monitoring: Review audit logs for unusual kernel-level activity or BPF program execution patterns that may indicate attempts to trigger verifier errors.

Compensating Controls: Restrict access to the bpf() system call using administrative policies or security modules like SELinux or AppArmor to prevent unauthorized users from loading eBPF programs.

Exploitation status

Public Exploit Available: Unknown.

Analyst recommendation

The risk posed by this kernel-level vulnerability is significant for multi-user systems where eBPF capabilities are enabled. Security teams should prioritize patching the kernel across all affected infrastructure to eliminate the possibility of local privilege escalation. Immediate deployment of the 7.2.6 update is the most effective method to mitigate this risk.

More Linux CVEs all →

History

CVE Brief tracked this CVE 4 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) from cvelistV5
  4. Analyst report written

Sources