CVE-2026-89605

Linux · Kernel

A memory management flaw in the Linux kernel eCryptfs subsystem allows a local user to cause a resource leak by failing to release a message context during send failures.

Executive summary

A high-severity resource management vulnerability in the Linux kernel eCryptfs subsystem could allow a local authenticated attacker to compromise system integrity and availability.

Vulnerability

The vulnerability exists in the ecryptfs_send_message_locked function, where a message context is moved to the allocated list but not properly returned to the free list if ecryptfs_send_miscdev fails. This requires local access with low privileges to trigger the failure condition, potentially resulting in memory exhaustion or inconsistent state.

Business impact

Successful exploitation of this flaw can lead to denial of service through memory exhaustion or potentially elevated system impact due to kernel-level memory corruption. Given the CVSS score of 7.8, this vulnerability poses a significant risk to the stability and security of systems utilizing the eCryptfs filesystem, particularly in multi-user environments where local privilege escalation is a primary concern.

Remediation

Immediate Action: Update the Linux kernel to version 6.12.109, 6.18.50, 7.2.4, or later depending on the active release branch.

Proactive Monitoring: Monitor system logs for kernel-level errors or unexpected crashes related to the eCryptfs subsystem.

Compensating Controls: Restrict access to the system for untrusted local users to minimize the exposure window for local privilege escalation vectors.

Exploitation status

Public Exploit Available: No

Analyst recommendation

This vulnerability represents a significant risk to kernel stability and should be addressed with high priority. Organizations should schedule kernel updates during the next maintenance cycle to ensure the patch is applied, thereby preventing potential exploitation by local users.

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