ZeroHour

CVE-2026-71220

niche

Stack out-of-bounds write in gfs2-utils gfs2_edit via crafted GFS2 images

CVSS 3.1
7.0 high
EPSS
<1%p3
Published
()
Modified
AI analysis

CVE-2026-71220 is a stack out-of-bounds write (CWE-787) in gfs2-utils, the Linux utilities suite for the GFS2 shared-disk cluster filesystem. In the gfs2_edit tool, the di_height field taken from on-disk inode metadata is used as an array index without bounds checking, so a crafted or corrupted GFS2 filesystem image can overflow a stack buffer. An attacker who can induce a user to process such an image locally may gain arbitrary code execution, consistent with the CVSS vector (AV:L/AC:H/PR:N/UI:R). Exposure is limited to systems with gfs2-utils installed — typically enterprise Linux servers in GFS2 shared-storage clusters — since the flaw requires deliberately running gfs2_edit against a malicious image. No public proof-of-concept, CISA KEV listing, or known exploitation exists, and EPSS estimates only a 0.1% probability of exploitation in the next 30 days.

What to do: No fixed version is given in the available data, so track Red Hat and distribution security advisories for gfs2-utils and apply the vendor's patched package as soon as it is released. Until then, avoid running gfs2_edit against untrusted or attacker-supplied GFS2 filesystem images. Confirm exposure by checking whether gfs2-utils is installed on cluster nodes (e.g., `rpm -q gfs2-utils` on RHEL systems).

Affected
Red Hat / gfs2-utils project gfs2-utils (gfs2_edit tool)
Estimated exposure
nichelow thousands of installed systems at most — GFS2 is deployed only where Linux shared-storage clustering is used, chiefly RHEL-style high-availability/Resilient Storage cluster nodes, a small subset of enterprise Linux servers, and gfs2_edit must be run manually against an…

Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.

Description

A stack out-of-bounds write vulnerability was found in gfs2-utils. In gfs2_edit, the di_height field from on-disk inode metadata is used as an array index without bounds checking, causing a stack buffer overflow that may lead to arbitrary code execution when processing crafted GFS2 filesystem images.

Weakness
CWE-787
Vector
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

In the news

No ingested article mentions this CVE yet.