Skip to content
Fencer Vulns
high 7.0

CVE-2026-71221 json

Gfs2-utils: gfs2-utils: stack out-of-bounds write via unchecked height in savemeta

published 2026-09-03 2 mo ago modified 2026-11-05 3 d ago also EUVD-2026-70449

cvss
7.0
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.1%
EPSS 0.1% chance of exploitation in 30 days, percentile 2%
public exploits
0
none known

Summary

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

Patch / fix

  • gfs2-utils Debian 14 3.6.1-2

debian advisories DEBIAN-CVE-2026-71221

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-71221 updated cvss 7.0

gfs2-utils: gfs2-utils: stack out-of-bounds write via unchecked height in savemeta

  • Red Hat Enterprise Linux 7 gfs2-utils 3.1.10-11.el7_9.1 Red Hat Enterprise Linux 8 gfs2-utils 3.1.10-11.el7_9.1 Red Hat Enterprise Linux 9 gfs2-utils 3.1.10-11.el7_9.1
    affected: workaround, no fix available

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
2 mo ago

Exploit prediction

0.13% chance of exploitation in the next 30 days, higher than 2% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.0 CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected products

  • Red Hat Red Hat Enterprise Linux 7
  • Red Hat Red Hat Enterprise Linux 8
  • Red Hat Red Hat Enterprise Linux 9

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.