CVE-2023-54099
published 2025-12-24CVE-2023-54099: In the Linux kernel, the following vulnerability has been resolved: fs: Protect reconfiguration of sb read-write from racing writes The reconfigure / remount…
PriorityP424low5.5
EPSS
0.19%
8.6th percentile
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/[email protected]/T/
Affected
17 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.52-1 (bookworm) | linux 6.1.52-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 8d0347f6c3a9d4953ddd636a31c6584da082e084 < 0336b42456e485fda1006b5b411e7372e20fbf03 | 0336b42456e485fda1006b5b411e7372e20fbf03 |
| linux | linux | >= 8d0347f6c3a9d4953ddd636a31c6584da082e084 < 7e4e87ec56aa6d008c64eab31b340a7c452b26cc | 7e4e87ec56aa6d008c64eab31b340a7c452b26cc |
| linux | linux | >= 8d0347f6c3a9d4953ddd636a31c6584da082e084 < 0ccfe21949bc9f706a86ee7351b74375c0745757 | 0ccfe21949bc9f706a86ee7351b74375c0745757 |
| linux | linux | >= 8d0347f6c3a9d4953ddd636a31c6584da082e084 < 295ef44a2abaf97d7a594b1d4c60d4be3738191f | 295ef44a2abaf97d7a594b1d4c60d4be3738191f |
| linux | linux | >= 8d0347f6c3a9d4953ddd636a31c6584da082e084 < 4abda85197ba5d695e6040d580b4b409ce0d3733 | 4abda85197ba5d695e6040d580b4b409ce0d3733 |
| linux | linux | >= 8d0347f6c3a9d4953ddd636a31c6584da082e084 < c541dce86c537714b6761a79a969c1623dfa222b | c541dce86c537714b6761a79a969c1623dfa222b |
| linux | linux_kernel | >= 0 < 5.10.191-1 | 5.10.191-1 |
| linux | linux_kernel | >= 0 < 6.1.52-1 | 6.1.52-1 |
| linux | linux_kernel | >= 0 < 6.4.11-1 | 6.4.11-1 |
| linux | linux_kernel | >= 0 < 6.4.11-1 | 6.4.11-1 |
| linux | linux_kernel | >= 5.1.0 < 5.4.253 | 5.4.253 |
| linux | linux_kernel | >= 5.11.0 < 5.15.126 | 5.15.126 |
| linux | linux_kernel | >= 5.16.0 < 6.1.45 | 6.1.45 |
| linux | linux_kernel | >= 5.5.0 < 5.10.190 | 5.10.190 |
| linux | linux_kernel | >= 6.2.0 < 6.4.10 | 6.4.10 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-vwq3-xpg9-vpx4: In the Linux kernel, the following vulnerability has been resolved:
fs: Protect reconfiguration of sb read-write from racing writes
The reconfigure
ghsa_unreviewed·2025-12-24
CVE-2023-54099 GHSA-vwq3-xpg9-vpx4: In the Linux kernel, the following vulnerability has been resolved:
fs: Protect reconfiguration of sb read-write from racing writes
The reconfigure
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 racin
OSV
CVE-2023-54099: In the Linux kernel, the following vulnerability has been resolved: fs: Protect reconfiguration of sb read-write from racing writes The reconfigure /
osv·2025-12-24
CVE-2023-54099 CVE-2023-54099: In the Linux kernel, the following vulnerability has been resolved: fs: Protect reconfiguration of sb read-write from racing writes The reconfigure /
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
OSV
fs: Protect reconfiguration of sb read-write from racing writes
osv·2025-12-24
CVE-2023-54099 fs: Protect reconfiguration of sb read-write from racing writes
fs: Protect reconfiguration of sb read-write from racing writes
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 read
Red Hat
kernel: fs: Protect reconfiguration of sb read-write from racing writes
vendor_redhat·2025-12-24·CVSS 5.5
CVE-2023-54099 [LOW] CWE-367 kernel: fs: Protect reconfiguration of sb read-write from racing writes
kernel: fs: Protect reconfiguration of sb read-write from racing writes
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'
Debian
CVE-2023-54099: linux - In the Linux kernel, the following vulnerability has been resolved: fs: Protect...
vendor_debian·2023
CVE-2023-54099 CVE-2023-54099: linux - In the Linux kernel, the following vulnerability has been resolved: fs: Protect...
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
No detection rules found.
No public exploits indexed.
Wiz
CVE-2023-54099 Impact, Exploitability, and Mitigation Steps | Wiz
blogs_wiz
CVE-2023-54099 CVE-2023-54099 Impact, Exploitability, and Mitigation Steps | Wiz
## CVE-2023-54099 :
Linux Kernel vulnerability analysis and mitigation
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
Bugzilla
CVE-2023-54099 kernel: fs: Protect reconfiguration of sb read-write from racing writes
bugzilla·2025-12-24
CVE-2023-54099 [LOW] CVE-2023-54099 kernel: fs: Protect reconfiguration of sb read-write from racing writes
CVE-2023-54099 kernel: fs: Protect reconfiguration of sb read-write from racing writes
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].
https://git.kernel.org/stable/c/0336b42456e485fda1006b5b411e7372e20fbf03https://git.kernel.org/stable/c/0ccfe21949bc9f706a86ee7351b74375c0745757https://git.kernel.org/stable/c/295ef44a2abaf97d7a594b1d4c60d4be3738191fhttps://git.kernel.org/stable/c/4abda85197ba5d695e6040d580b4b409ce0d3733https://git.kernel.org/stable/c/7e4e87ec56aa6d008c64eab31b340a7c452b26cchttps://git.kernel.org/stable/c/c541dce86c537714b6761a79a969c1623dfa222b
2025-12-24
Published