CVE-2023-54099

published 24 Dec 2025 · updated 11 May 2026

fs: Protect reconfiguration of sb read-write from racing writes

5.0MediumEPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 0336b42456e485fda1006b5b411e7372e20fbf03, Kernel 0ccfe21949bc9f706a86ee7351b74375c0745757, Kernel 295ef44a2abaf97d7a594b1d4c60d4be3738191f and 3 more.

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/

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=5.1, >=8d0347f6c3a9d4953ddd636a31c6584da082e084 <0336b42456e485fda1006b5b411e7372e20fbf03, >=8d0347f6c3a9d4953ddd636a31c6584da082e084 <0ccfe21949bc9f706a86ee7351b74375c0745757, >=8d0347f6c3a9d4953ddd636a31c6584da082e084 <295ef44a2abaf97d7a594b1d4c60d4be3738191f, >=8d0347f6c3a9d4953ddd636a31c6584da082e084 <4abda85197ba5d695e6040d580b4b409ce0d3733, >=8d0347f6c3a9d4953ddd636a31c6584da082e084 <7e4e87ec56aa6d008c64eab31b340a7c452b26cc, >=8d0347f6c3a9d4953ddd636a31c6584da082e084 <c541dce86c537714b6761a79a969c1623dfa222b0336b42456e485fda1006b5b411e7372e20fbf03, 0ccfe21949bc9f706a86ee7351b74375c0745757, 295ef44a2abaf97d7a594b1d4c60d4be3738191f, 4abda85197ba5d695e6040d580b4b409ce0d3733, 7e4e87ec56aa6d008c64eab31b340a7c452b26cc, c541dce86c537714b6761a79a969c1623dfa222b

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2023-54099 severity on Zeptric[![CVE-2023-54099](https://zeptric.io/badge/cve/CVE-2023-54099.svg)](https://zeptric.io/cve/CVE-2023-54099)