The vulnerability arises when the GFS2 filesystem driver attempts to flush pending log work during an unmount operation. If the file system descriptor’s journal descriptor has already been freed, the gfs2_log_flush() routine can access a NULL pointer, causing a kernel panic. Because the crash occurs in kernel space, a successful exploitation would lead to a denial‑of‑service and could allow local privilege escalation if the attacker can trigger the unmount while a privileged process is unresponsive.

The issue affects the Linux kernel when the GFS2 filesystem module is compiled and used. Any kernel version prior to the commit that introduced the NULL pointer check is vulnerable. The specific affected build or version is not enumerated in the data; systems running older kernels should verify the presence of the commit 35264909e9d1 or apply a later stable kernel.

The CVSS score is not provided and EPSS is not available, indicating that a quantifiable assessment is not available in the public data. The vulnerability is listed as not included in CISA KEV, suggesting no currently known active exploit. The likely attack vector is local or through a privilege‑able user, as unmounting a filesystem normally requires root or CAP_SYS_ADMIN capabilities. Given the lack of public exploitation information, the risk remains moderate to high for systems that use GFS2 and run susceptible kernels, but the exploitation complexity remains non‑trivial.