CVE-2026-53049: gfs2: add some missing log locking

criticalCVSS 9.8CVE-2026-53049

CSIRTS triage

vendor: null product: gfs2Other

What: Missing log locking in gfs2 could lead to critical issues.
Who is affected: Deployments using gfs2 are affected.
Urgency: Remediation is critical due to the high severity with a CVSS score of 9.8.
Action: Update to the latest version of gfs2.

AI-assisted analysis generated from the source advisory — verify against the original.

⚡ Watch gfs2

Get an email when a new gfs2 advisory drops — max one per day, one-click unsubscribe.

Details

Source: Microsoft Security Response Center (INTL · vendor-psirt · site)
Severity: critical — CVSS 9.8
Published: 2026-06-09
Exploitation: Not in CISA KEV at last sync

Original advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-53049

Exploitation outlook

EPSS (FIRST.org) estimates each CVE’s probability of exploitation in the next 30 days — here is the CSIRTS.com read on those numbers.

Low exploitation riskCVE-2026-530490.51% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 40% of all scored CVEs.

Referenced CVEs

CVE	CSIRTS overview	External
CVE-2026-53049	coverage & exploitation status	NVD · CVE.org

Same CVEs, other sources

How other CERTs, PSIRTs and databases cover the vulnerabilities in this advisory.

unknownMultiple vulnerabilities in Debian LTS Linux kernel (July 10, 2026)cert-fr-avis

Recent advisories for gfs2

A cluster of recent advisories against the same product widens the attack surface — attackers routinely chain freshly published CVEs on one product, so review these together.

mediumCVE-2026-53048: gfs2: prevent NULL pointer dereference during unmountmsrc · 2026-06-09