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

> A race condition in the Linux kernel GFS2 filesystem log flushing can lead to system instability or denial of service.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Jun 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-53049, DEBIAN-CVE-2026-53049, GHSA-7q4j-gqp5-6p93, ROOT-OS-DEBIAN-11-CVE-2026-53049, ROOT-OS-DEBIAN-12-CVE-2026-53049, ROOT-OS-UBUNTU-2204-CVE-2026-53049, ROOT-OS-UBUNTU-2404-CVE-2026-53049, UBUNTU-CVE-2026-53049

## What is CVE-2026-53049?

CVE-2026-53049 is a critical vulnerability in Linux kernel, published on 24 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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().

Weakness: CWE-667 (Improper Locking), CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2026-53049?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2026-53049?

Apply the vendor's patch.

## Is CVE-2026-53049 being exploited?

There is no known exploitation of CVE-2026-53049 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-53049 and fix it if it is affected.

What it is: CVE-2026-53049 is a critical vulnerability in Linux kernel, published on 24 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-53049 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-53049/ (Markdown: https://insights.sbomify.com/CVE-2026-53049/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-53049
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-53049
- OSV: https://osv.dev/vulnerability/CVE-2026-53049

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-53049/
Summaries are generated and may contain mistakes; the official description above is the record.