A stack overflow vulnerability was found in gfs2-utils. The metadata walk code in metawalk.c uses alloca() with an untrusted inode height value from on-disk metadata without bounds validation, causing stack exhaustion and a denial of service when processing crafted GFS2 filesystem images.
CVE-2026-71224
Score 4.7 from GitHub Security Advisory published 2026-09-03. a secondary CVSS source baseline 4.7; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.7
- EG Score
- 4.7(high)
- EG Risk
- 21(Track)EG Risk 21/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity47% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 2%
- KEV
- Not listed
Published
September 3, 2026
Last Modified
September 3, 2026
Advisory Details (1)
Auto-updated Sep 3, 20262511397 – (CVE-2026-71224) CVE-2026-71224 gfs2-utils: gfs2-utils: stack overflow via alloca(i_height) in metadata walk
https://bugzilla.redhat.com/show_bug.cgi?id=2511397Vendor Advisories for CVE-2026-71224(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(3 across 3 ecosystems)
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| gfs2-utils | 3.5.0-2, 3.5.1-1, 3.5.1-2, 3.6.0-1, 3.6.1-1 | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| gfs2-utils | 3.6.1-1 | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| gfs2-utils | 3.6.1-1 | — | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 24× in last 7d / 54× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-20 20:16 UTCEPSS rescore
- 2026-09-20 11:55 UTCEG score recompute
- 2026-09-20 11:55 UTCVendor advisory
- 2026-09-20 11:55 UTCGHSA enrichment
- 2026-09-19 12:50 UTCEG score recompute
- 2026-09-19 12:50 UTCVendor advisory
- 2026-09-19 12:50 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 13:57 UTCEG score recompute
- 2026-09-18 13:57 UTCVendor advisory
- 2026-09-18 13:57 UTCGHSA enrichment
- 2026-09-17 15:03 UTCVendor advisory
- 2026-09-17 15:03 UTCGHSA enrichment
- 2026-09-16 16:09 UTCEG score recompute
- 2026-09-16 16:09 UTCVendor advisory
- 2026-09-16 16:09 UTCGHSA enrichment
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 17:16 UTCEG score recompute
- 2026-09-15 17:16 UTCVendor advisory
- 2026-09-15 17:16 UTCGHSA enrichment
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-14 18:23 UTCVendor advisory
- 2026-09-14 18:23 UTCGHSA enrichment
- 2026-09-13 19:00 UTCEG score recompute
Show 29 moreShow fewer
- 2026-09-13 19:00 UTCVendor advisory
- 2026-09-13 19:00 UTCGHSA enrichment
- 2026-09-12 20:07 UTCVendor advisory
- 2026-09-12 20:07 UTCGHSA enrichment
- 2026-09-11 21:14 UTCEG score recompute
- 2026-09-11 21:14 UTCVendor advisory
- 2026-09-11 21:14 UTCGHSA enrichment
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-10 22:21 UTCEG score recompute
- 2026-09-10 22:21 UTCGHSA enrichment
- 2026-09-10 09:35 UTCEPSS rescore
- 2026-09-09 23:28 UTCGHSA enrichment
- 2026-09-08 23:10 UTCEG score recompute
- 2026-09-08 23:09 UTCGHSA enrichment
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-07 14:50 UTCGHSA enrichment
- 2026-09-06 14:58 UTCEG score recompute
- 2026-09-06 14:58 UTCGHSA enrichment
- 2026-09-06 13:48 UTCEPSS rescore
- 2026-09-05 16:05 UTCEG score recompute
- 2026-09-05 16:05 UTCGHSA enrichment
- 2026-09-04 17:12 UTCEG score recompute
- 2026-09-04 17:11 UTCGHSA enrichment
- 2026-09-03 18:18 UTCEG score recompute
- 2026-09-03 18:18 UTCGHSA enrichment
- 2026-09-03 13:14 UTCEG score recompute
- 2026-09-03 13:05 UTCEG score recompute
- 2026-09-03 12:46 UTCEG score recompute
- 2026-09-03 12:44 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-71224?
When was CVE-2026-71224 disclosed?
Is CVE-2026-71224 actively exploited?
What is the CVSS score of CVE-2026-71224?
How do I remediate CVE-2026-71224?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-71224
Is Your Infrastructure Affected by CVE-2026-71224?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.