Skip to main content

Linux Kernel CVE-2026-53049

| EUVDEUVD-2026-38917 CRITICAL
Improper Locking (CWE-667)
2026-06-24 Linux GHSA-7q4j-gqp5-6p93
Information Disclosure Linux
Critical
Disputed · 9.8 Vendor: Linux
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Local activity on GFS2-mounted node
  2. Delivery
    Generate concurrent journal transactions
  3. Exploit
    gfs2_logd flushes AIL without sd_log_flush_lock
  4. Execution
    Race corrupts journal/AIL state
  5. Impact
    Kernel crash or filesystem corruption

Vulnerability Assessment

Weakness
CWE
CWE-667
ASVS 5.0
V15 - Secure Coding and Architecture Proper locking
Exploitation Conditions

Requires the target system to have a GFS2 filesystem mounted and actively servicing concurrent transactions, so that the gfs2_logd flush thread races with in-flight journal operations on the AIL - the exact prerequisite is use of the GFS2 cluster filesystem, which is not a default configuration on typical servers. Exploitation is fundamentally limited: it needs local activity on the node (not network reachability despite the AV:N in the supplied vector), depends on non-deterministic lock-race timing rather than a controllable input, and has no effect on systems that do not use GFS2. These limiting factors place realistic impact well below the input's 9.8 rating.
Impact

The signals conflict sharply. The supplied CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N, score 9.8) describes a remote, unauthenticated, full-impact RCE-class flaw, but the description is a local kernel locking fix in a filesystem journaling thread with no network-reachable trigger - this is the well-known pattern of auto-generated maximal CVSS scores for Linux kernel CVEs and should be treated as inaccurate. EPSS (0.17%, 7th percentile) and the absence of KEV listing or any POC corroborate low real-world exploitation likelihood. There is no SSVC decision data provided; automatability is effectively low because triggering the race requires concurrent GFS2 transaction load on a mounted GFS2 volume. Realistic impact is denial of service (kernel crash/hang) or on-disk/journal corruption on GFS2 cluster nodes, not remote compromise. The vendor 'Information Disclosure' tag is not substantiated by the description and is likely a generic label. Net: low operational priority outside environments actively running GFS2, where it should be patched as a stability/integrity fix.
Exploit ScenarioDerived

On a high-availability cluster node mounting a GFS2 volume, heavy concurrent file I/O generates journal transactions while the gfs2_logd thread flushes the log without the required lock, causing the AIL to be modified mid-transaction and resulting in a kernel crash or journal/data corruption that can take the node - or the clustered filesystem - offline. No public exploit code is known, and triggering it depends on workload timing rather than a deliberate crafted input.
Act Now Prioritize within 24-48h. Why: CRITICAL severity.
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jun 28, 2026

Concurrency-induced data corruption in the Linux kernel GFS2 cluster filesystem occurs because gfs2_logd() invokes the log-flushing helpers gfs2_ail1_start(), gfs2_ail1_wait(), and gfs2_ail1_empty() without holding sdp->sd_log_flush_lock, allowing these routines to race with concurrent journal transactions that the lock is meant to serialize. The defect affects systems mounting GFS2 volumes and is fixed by adding a non-locking __gfs2_log_flush() helper and acquiring sd_log_flush_lock in gfs2_logd before flushing. No public exploit identified at time of analysis, and EPSS is low (0.17%, 7th percentile), consistent with a local filesystem race rather than a remotely weaponizable flaw despite the input's 9.8 score.

RemediationAI

Vendor-released patch: upgrade to a fixed stable kernel - 5.15.209, 6.1.175, 6.6.141, 6.12.91, 6.18.33, 7.0.10, or 7.1 or later on the matching branch (commits via https://git.kernel.org/stable/c/fe2c8d051150b90b3ccb85f89e3b1d636cb88ec8 and the other stable commit references). Apply your distribution's corresponding kernel update once it ships the backport. Because the bug only manifests on GFS2, the most effective compensating control where patching is deferred is to avoid GFS2: migrate affected workloads to an alternative shared filesystem (e.g., OCFS2) or take the GFS2 volume offline; if GFS2 must remain mounted, reduce concurrent write/transaction pressure and monitor for kernel log warnings, soft lockups, or filesystem withdrawal events, accepting that this only narrows the race window rather than closing it. There is no network-facing control to apply since the trigger is local kernel activity.

Affected VersionsENISA

Linux 5e4c7632aae1cce137792647f4fb6f599d1da893 <fe2c8d051150b90b3ccb85f89e3b1d636cb88ec8
Linux patch: 7.0.10
Linux patch: 5.15.209
Linux patch: 0
Linux patch: 6.12.91
Linux patch: 6.18.33
Linux 5e4c7632aae1cce137792647f4fb6f599d1da893 <3b28eb75afe520972bacc833850c2b30aa0824cd
Linux 5.7
Linux 5e4c7632aae1cce137792647f4fb6f599d1da893 <ca95342cb1b39062a03c115830286f0a426053d5
Linux patch: 6.6.141
Linux 5e4c7632aae1cce137792647f4fb6f599d1da893 <98e8bf249c790d56de1abc4a5f8bd68035a00921
Linux 5e4c7632aae1cce137792647f4fb6f599d1da893 <f2f225cf505ac016132ded21690f3ba0a080a4e8
Linux 5e4c7632aae1cce137792647f4fb6f599d1da893 <49d9be0722da3a4a893ba905720cba1921834ec3
Linux 5e4c7632aae1cce137792647f4fb6f599d1da893 <bf5fcd9c37c2546beaf7b401d31aefd89017dc3d
Linux patch: 7.1
Linux patch: 6.1.175

Affected Packages

euvd linux no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Sign in to check
Technical ContextAI · show details

GFS2 (Global File System 2) is a shared-disk clustered filesystem used in Red Hat/Pacemaker high-availability clusters where multiple nodes mount the same block device. It maintains a journal protected by an Active Items List (AIL); the sd_log_flush_lock serializes log-flush operations against in-flight transactions. The gfs2_logd kernel thread periodically flushes the journal, but the buggy code path called gfs2_ail1_start/wait/empty outside this lock, so the AIL could be manipulated concurrently with an active transaction - a classic data-race / missing-synchronization condition (the input lists CWE as N/A, but this maps to CWE-667 Improper Locking / CWE-362 race condition). The CPE data only generically identifies cpe:2.3:a:linux:linux:*, so exact affected component (fs/gfs2/log.c) is derived from the patch description rather than structured CPE.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources
Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

Sources disagree (Medium–Critical)
Vendor (Linux) PRIMARY 9.8 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 6.3 MEDIUM

Local trigger on a GFS2 node (AV:L), non-deterministic lock race (AC:H), requires local access to drive filesystem I/O (PR:L); impact is corruption and crash (I:H/A:H), no confidentiality disclosure (C:N).

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:H
4.0 AV:L/AC:H/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N
SUSE 5.7 HIGH
AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:H
Red Hat 7.0 MEDIUM

vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.

CVSS VectorVendor: Linux

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

4
CVSS changed
Jun 28, 2026 - 08:22 NVD
9.8 (CRITICAL)
Patch available
Jun 24, 2026 - 18:02 EUVD
CVE Published
Jun 24, 2026 - 16:29 cve.org
CRITICAL 9.8
CVE Published
Jun 24, 2026 - 16:29 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

In the Linux kernel, the following vulnerability has been resolved:

gfs2: add some missing log locking

Function gfs2_logd() calls the log flushing functions gfs2_ail1_start(), gfs2_ail1_wait(), and gfs2_ail1_empty() without holding sdp->sd_log_flush_lock, but these functions require exclusion against concurrent transactions.

To fix that, add a non-locking __gfs2_log_flush() function. Then, in gfs2_logd(), take sdp->sd_log_flush_lock before calling the above mentioned log flushing functions and __gfs2_log_flush().

Executive ViewAI

Why It Matters

CVE-2026-53049 affects the Linux kernel GFS2 cluster filesystem, introducing potential data corruption through a race condition in journal transaction handling. Organizations operating shared-storage clustering infrastructure with GFS2 volumes face business continuity and data integrity risks. A vendor patch is available; immediate assessment and testing is required for production GFS2 environments to prevent potential data loss.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.2%
Top 93% exploitable
Prevalence
Low
GFS2 is a niche clustered filesystem deployed mainly in HA clusters
Data Quality
6 sources
Confidence: High
EUVD NVD CVE.org EPSS MSRC Vendor VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
High

Priority Score

49
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +49
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information Disclosure MEDIUM

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Same weakness CWE-667 – Improper Locking

View all
CVE-2025-43510 HIGH POC
7.8
CVE-2019-5886 CRITICAL POC
9.8
CVE-2020-13246 HIGH POC
7.5
CVE-2019-15513 HIGH POC
7.5
CVE-2019-11599 HIGH POC
7.0
CVE-2023-21400 MEDIUM POC
6.7
CVE-2021-20291 MEDIUM POC
6.5
CVE-2026-64068 CRITICAL
9.8

Same technique Information Disclosure

View all
CVE-2019-2725 CRITICAL POC
9.8
CVE-2021-34523 CRITICAL POC
9.0
CVE-2013-2251 CRITICAL POC
9.8
CVE-2017-5638 CRITICAL POC
9.8
CVE-2025-24813 CRITICAL POC
9.8
CVE-2025-68613 HIGH POC
8.8
CVE-2015-1701 HIGH POC
7.8
CVE-2017-0147 HIGH POC
7.5

Vendor StatusVendor

SUSE

Severity: Important
Product Status
Container suse/sl-micro/6.0/base-os-container:2.1.3-7.177 Container suse/sl-micro/6.1/base-os-container:2.2.1-5.155 Affected
Container suse/sl-micro/6.0/rt-os-container:2.1.3-7.206 Container suse/sl-micro/6.1/rt-os-container:2.2.1-5.152 Affected
Image SLES15-SP7-Azure-3P Image SLES15-SP7-Azure-Basic Image SLES15-SP7-Azure-Standard Image SLES15-SP7-HPC-Azure Affected
Image SLES15-SP7-BYOS-Azure Image SLES15-SP7-BYOS-GCE Image SLES15-SP7-CHOST-BYOS-Aliyun Image SLES15-SP7-CHOST-BYOS-Azure Image SLES15-SP7-CHOST-BYOS-EC2 Image SLES15-SP7-CHOST-BYOS-GCE Image SLES15-SP7-CHOST-BYOS-GDC Image SLES15-SP7-CHOST-BYOS-SAP-CCloud Image SLES15-SP7-EC2 Image SLES15-SP7-EC2-ECS-HVM Image SLES15-SP7-GCE Image SLES15-SP7-HPC-BYOS-Azure Image SLES15-SP7-HPC-BYOS-EC2 Image SLES15-SP7-HPC-BYOS-GCE Image SLES15-SP7-Hardened-BYOS-Azure Image SLES15-SP7-Hardened-BYOS-EC2 Image SLES15-SP7-Hardened-BYOS-GCE Image SLES15-SP7-SAPCAL-Azure Image SLES15-SP7-SAPCAL-EC2 Image SLES15-SP7-SAPCAL-GCE Affected
Image SLES15-SP7-SAP-Azure Image SLES15-SP7-SAP-Azure-3P Image SLES15-SP7-SAP-BYOS-Azure Image SLES15-SP7-SAP-BYOS-EC2 Image SLES15-SP7-SAP-BYOS-GCE Image SLES15-SP7-SAP-EC2 Image SLES15-SP7-SAP-GCE Image SLES15-SP7-SAP-Hardened-Azure Image SLES15-SP7-SAP-Hardened-BYOS-Azure Image SLES15-SP7-SAP-Hardened-BYOS-EC2 Image SLES15-SP7-SAP-Hardened-BYOS-GCE Image SLES15-SP7-SAP-Hardened-GCE Affected

References

Advisories & patches
ADVISORY https://nvd.nist.gov/vuln/detail/CVE-2026-53049 ADVISORY https://ubuntu.com/security/notices/USN-8566-1 ADVISORY https://ubuntu.com/security/notices/USN-8567-1 ADVISORY https://ubuntu.com/security/notices/USN-8568-1 ADVISORY https://vuldb.com/vuln/373430 ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:22742/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:22769/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:3130/ ADVISORY https://www.suse.com/support/update/SUSE-SU-2026:3166/ REF https://git.kernel.org/stable/c/3b28eb75afe520972bacc833850c2b30aa0824cd REF https://git.kernel.org/stable/c/49d9be0722da3a4a893ba905720cba1921834ec3 REF https://git.kernel.org/stable/c/98e8bf249c790d56de1abc4a5f8bd68035a00921 REF https://git.kernel.org/stable/c/bf5fcd9c37c2546beaf7b401d31aefd89017dc3d REF https://git.kernel.org/stable/c/ca95342cb1b39062a03c115830286f0a426053d5 REF https://git.kernel.org/stable/c/f2f225cf505ac016132ded21690f3ba0a080a4e8 REF https://git.kernel.org/stable/c/fe2c8d051150b90b3ccb85f89e3b1d636cb88ec8

Search Externally

GitHub PoC Exploit-DB PacketStorm Snyk Rapid7 Nuclei Templates Trickest PoC
Back

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy