A use-after-free vulnerability in libfuse versions 3.18.0 through 3.18.1 poses a significant risk of arbitrary code execution for local attackers targeting containerized environments.

This flaw is a use-after-free vulnerability (CWE-416) within the io_uring subsystem of libfuse. It occurs when thread creation fails due to resource exhaustion, causing a dangling pointer to be stored in the session state, which can be triggered by a local attacker with low privileges.

The vulnerability carries a CVSS score of 7.8, indicating a high severity risk. Successful exploitation allows a local attacker to achieve arbitrary code execution or cause a denial of service, which could compromise the integrity and availability of sensitive data processed within containerized environments.

Immediate Action: Update the libfuse library to version 3.18.2 or later to incorporate the vendor-provided fix.

Proactive Monitoring: Monitor system logs for repeated process crashes or unusual resource exhaustion errors related to FUSE filesystem operations.

Compensating Controls: Implement strict cgroup limits to manage resource allocation and consider restricting access to FUSE mount capabilities for untrusted local users.

Public Exploit Available: Yes, a public proof-of-concept exists as documented in GitHub repositories.

Given the potential for arbitrary code execution in containerized environments, organizations should prioritize updating libfuse to version 3.18.2 immediately. This remediation is essential to eliminate the use-after-free condition and secure the filesystem process against local exploitation attempts.