CVE-2026-93192

Linux · Kernel

A dangling pointer vulnerability in the Linux kernel v3d driver allows for potential memory corruption due to improper cleanup during a failed fence creation process.

Executive summary

A memory management flaw in the Linux kernel v3d driver could allow a local attacker to cause system instability or potential code execution.

Vulnerability

This is a memory management vulnerability involving a dangling pointer in the v3d driver, which occurs when a job is assigned to an active queue before a fence creation failure, without subsequent cleanup. An attacker with local access and low privileges can trigger this error path to manipulate kernel memory.

Business impact

The vulnerability carries a CVSS score of 7.8, reflecting its potential for high impact on confidentiality, integrity, and availability. Because this flaw exists within the kernel, successful exploitation could lead to full system compromise, unauthorized data access, or a kernel panic resulting in denial of service for critical infrastructure components.

Remediation

Immediate Action: Update the Linux kernel to version 6.12.110, 6.18.52, 7.2.6, or a later stable release provided by your distribution.

Proactive Monitoring: Monitor system logs for kernel oops or crash reports specifically related to the v3d driver or GPU memory management failures.

Compensating Controls: Restrict access to the system for untrusted local users to prevent the triggering of this specific driver path, as the attack vector requires local access.

Exploitation status

Public Exploit Available: Unknown

Analyst recommendation

Given the high severity and the nature of kernel-level vulnerabilities, organizations should prioritize patching affected Linux distributions as soon as stable updates are released by their respective vendors. While the attack vector is local, the potential for privilege escalation makes this a significant risk for multi-tenant environments or systems where untrusted code execution is possible.

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