A premature release of memory in the GFS2 file system write path can lead to a use-after-free vulnerability, risking system stability.

The inline data buffer head (dibh) is released prematurely in gfs2_iomap_begin() via release_metapath(), while the iomap structure still references the buffer. This creates a use-after-free condition when the kernel attempts to access the data.

This vulnerability could result in data corruption or a system crash on servers utilizing the GFS2 cluster file system. With a CVSS score of 7.8, the impact on data integrity and system uptime is significant, particularly in high-availability environments.

Immediate Action: Patch the Linux kernel to the version provided by your vendor that addresses the GFS2 inline data write path issue.

Proactive Monitoring: Monitor GFS2-related error logs and file system integrity checks for signs of corruption.

Compensating Controls: If immediate patching is not feasible, restrict the use of GFS2 inline data features if possible.

Public Exploit Available: false

Organizations relying on GFS2 should prioritize this update to avoid potential file system instability. Ensure that kernel updates are applied to all nodes in the GFS2 cluster to maintain a secure and stable environment.