CVE-2026-71222: Gfs2-utils: gfs2-utils: heap out-of-bounds read via unchecked ea_num_ptrs in extended attribute processing

Published Aug 5, 2026
·
Updated

A flaw was found in gfs2-utils. The eanumptrs field from on-disk extended attribute metadata is used as a loop count in savemeta.c and metawalk.c without bounds validation. The eanumptrs field is a u8 (max 255). Each iteration reads a pointer (8 bytes) plus name data. With eanumptrs=255 and a 512-byte block buffer, the loop reads up to 1384 bytes past the buffer boundary, causing a heap out-of-bounds read. This may disclose sensitive heap memory contents through tool output or error messages, and the significant over-read (2.7x the allocation) has a non-trivial probability of crossing a page boundary into unmapped memory, causing a crash.

Other sources

A heap out-of-bounds read vulnerability was found in gfs2-utils. The eanumptrs field from on-disk extended attribute metadata is consumed without bounds validation, causing a heap buffer over-read that may disclose sensitive memory contents or cause a crash when processing crafted GFS2 filesystem images.

NVD

Gfs2-utils: gfs2-utils: heap out-of-bounds read via unchecked eanumptrs in extended attribute processing

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 that use gfs2-utils to process a crafted GFS2 filesystem image are exposed. The affected parsing paths are in savemeta.c and metawalk.c during extended-attribute metadata handling.

2

What does an attacker need to exploit it?

An attacker needs to cause gfs2-utils to process GFS2 on-disk metadata with a malicious ea_num_ptrs value. The supplied severity vector indicates local attack access, no privileges required, and user interaction required.

3

What is the likely impact during processing?

The out-of-bounds read can expose heap memory through tool output or error messages. It can also crash the tool if the over-read crosses into an unmapped memory page.

4

How can I determine whether a filesystem image is maliciously formed?

Inspect the extended-attribute metadata for an ea_num_ptrs value that is not valid for the available block buffer. A value of 255 can drive reads far beyond a 512-byte block buffer.

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