CVE-2026-53049: gfs2: add some missing log locking
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().
Metrics
- CVSS v3.1
- 9.8
- Severity
- CRITICAL
- Fixed in
- 0
- Affected Products
- 2
HarborGuard Analysis
Synopsis
This is a missing lock (race condition) vulnerability in the Linux kernel's GFS2 clustered filesystem driver. It is reachable over the network without any authentication or user interaction, based on the CVSS:3.1/AV:N/AC:L/PR:N/UI:N vector. Successful exploitation gives an attacker full read, write, and denial-of-service capability against the affected system. Patched-image rebuilds at versions 5.15.209, 6.1.175, and the named commit SHAs are available on HarborGuard for environments running an affected kernel version.
HarborGuard Coverage
Detection is available across every HarborGuard environment: the CVE is ingested from upstream feeds within minutes of publication and matched against all customer images, including custom-built images that carry an affected kernel version. Any image in a connected registry or CI pipeline is eligible for this matching without additional configuration.
AvailableHarborGuard scores this finding at CVSS 9.8 (Critical) and weights it against each environment's compliance policy to determine routing priority. Triage results are delivered to the appropriate team inbox within each customer organization based on configured ownership rules.
AvailableA patched-image rebuild at the fix versions (5.15.209, 6.1.175, or the upstream commit SHAs) becomes available on HarborGuard as soon as the upstream fix is confirmed. For customers who opt into auto-remediation, HarborGuard triggers a rebuild, runs a regression test suite, and opens a pull request against affected workloads automatically.
AvailableExploit Conditions
- Network reachabilityRequired
The vulnerable code path is reachable over the network, meaning an attacker must be able to send requests to the exposed service; no local shell or physical access is required.
- AuthenticationNot required
No credentials or account of any privilege level are needed to trigger the vulnerability.
- Victim interactionNot required
The exploit completes without any action from a logged-in user or administrator on the target system.
- Attack complexityDetail
Attack complexity is Low, meaning the exploit is reliable and requires no special environmental conditions, race-window timing, or memory-layout knowledge beyond sending a crafted request.
Blast Radius
- A successful attacker reads arbitrary kernel memory, including stored credentials, session tokens, and filesystem data.
- A successful attacker writes to kernel memory or filesystem structures, corrupting persisted data or escalating privileges.
- A successful attacker crashes the affected kernel or filesystem subsystem, taking down all workloads on the host.
- Because the GFS2 driver is a shared clustered filesystem component, a single exploited node can disrupt other nodes sharing the same GFS2 volume.
How HarborGuard Handles This
Available on HarborGuard: detection for CVE-2026-53049 is active across all connected registries and pipelines, matching images that carry a kernel version below 5.15.209 or 6.1.175 or that predate the named upstream commits. For customers who opt into auto-remediation, HarborGuard generates a rebuilt image at the patched version, runs a regression test suite against it, and opens a pull request against affected workloads; for Critical-severity issues, the median time from CVE publication to a merged patch PR is around 90 minutes in environments with auto-remediation enabled. Where compliance policy does not permit automated remediation, HarborGuard surfaces the finding with full CVSS detail and fix-version guidance so engineering teams can act manually. Because this is a kernel-level race condition in the GFS2 log flush path, customers who cannot immediately rebuild should consider isolating affected nodes from untrusted network traffic via network policy rules and restricting GFS2 volume access to known workloads as a compensating control while the patched image is prepared.
Fix available
- Linux / Linux< 3b28eb75afe520972bacc833850c2b30aa0824cd (from 5e4c7632aae1cce137792647f4fb6f599d1da893) · < ca95342cb1b39062a03c115830286f0a426053d5 (from 5e4c7632aae1cce137792647f4fb6f599d1da893) · < bf5fcd9c37c2546beaf7b401d31aefd89017dc3d (from 5e4c7632aae1cce137792647f4fb6f599d1da893) · < f2f225cf505ac016132ded21690f3ba0a080a4e8 (from 5e4c7632aae1cce137792647f4fb6f599d1da893) · < 49d9be0722da3a4a893ba905720cba1921834ec3 (from 5e4c7632aae1cce137792647f4fb6f599d1da893) · < 98e8bf249c790d56de1abc4a5f8bd68035a00921 (from 5e4c7632aae1cce137792647f4fb6f599d1da893)
- Linux / Linux5.7Fixed in 0, 5.15.209, 6.1.175, 6.6.141, 6.12.91, 6.18.33, 7.0.10, 7.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H