CVE-2026-71220: Gfs2-utils: gfs2-utils: stack out-of-bounds write via unchecked di_height in gfs2_edit

Published Aug 5, 2026
·
Updated

A flaw was found in gfs2-utils. In the gfs2edit tool, the metapathtolblock() function in extended.c uses the diheight field from on-disk inode metadata as an array index into a fixed-size stack array factor[GFS2MAXMETAHEIGHT] (10 elements) without bounds validation. An attacker can craft a GFS2 filesystem image with diheight exceeding 10 (up to 65535) to write past the end of the array, corrupting adjacent stack memory including saved registers and the return address. The subsequent loop (factor[h] = factor[h+1] sbd.sdinptrs) amplifies the corruption by writing additional entries past the array boundary. This is a classic stack buffer overflow that may allow arbitrary code execution when gfs2edit processes the crafted image. The Linux kernel GFS2 driver validates diheight against sdmaxheight in gfs2dinodein(), but the userspace gfs2-utils performs no equivalent validation.

Other sources

A stack out-of-bounds write vulnerability was found in gfs2-utils. In gfs2edit, the diheight 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.

NVD

Gfs2-utils: gfs2-utils: stack out-of-bounds write via unchecked diheight in gfs2edit

Microsoft

Affected Software

4 affected components
gfs2-utils
redhat Enterprise Linux=7.0
redhat Enterprise Linux=8.0
redhat Enterprise Linux=9.0

Event History

Aug 5, 2026
Data Sourced
via Red Hat·08:40 AM
DescriptionSeverityAffected Software
Sep 3, 2026
CVE Published
via MITRE·12:23 PM
Data Sourced
via MITRE·12:23 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·01:06 PM
DescriptionSeverityWeaknessAffected Software
Sep 9, 2026
Data Sourced
via Microsoft·08:01 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who is exposed to this issue?

Systems are exposed when gfs2_edit processes a crafted GFS2 filesystem image. The attacker needs to provide an image containing inode metadata with an oversized di_height value and have a user process that image with the vulnerable userspace tool.

2

Does the Linux kernel's GFS2 validation protect gfs2_edit?

No. The kernel GFS2 driver validates di_height against sd_max_height, but gfs2-utils does not perform equivalent validation in the affected gfs2_edit code path.

3

What can be done before a fix is available?

Do not run gfs2_edit against untrusted or externally supplied GFS2 filesystem images. Treat images with inode di_height values greater than 10 as unsafe for processing by the affected tool.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203