cveboard RSS feed

CVE-2023-54099

CVE.org · Published

Historical CVEsJSONAI instructions

Record status
Published
Identifier year (not publication year)
2023
Source publication
Source updated
Imported by cveboard
Source snapshot
cve_2026-10-24_midnight_baseline ·

Plain text

CNA source text (English)

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 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/

Scoped product and version facts

Fix information unknown; no fixed version is derived here. Missing information does not prove that no fix exists.

Exploitation unknown; this catalogue does not assess exploitation.

Linux

Vendor
Linux
Product
Linux
Platforms
Unknown
Default status
unaffected
Linux · Scoped product and version facts
Version (version)Status (status)Version scheme (versionType)Exclusive end (lessThan)Inclusive end (lessThanOrEqual)Status changes (at → status)
8d0347f6c3a9d4953ddd636a31c6584da082e084affectedgit0336b42456e485fda1006b5b411e7372e20fbf03UnavailableNone listed
8d0347f6c3a9d4953ddd636a31c6584da082e084affectedgit7e4e87ec56aa6d008c64eab31b340a7c452b26ccUnavailableNone listed
8d0347f6c3a9d4953ddd636a31c6584da082e084affectedgit0ccfe21949bc9f706a86ee7351b74375c0745757UnavailableNone listed
8d0347f6c3a9d4953ddd636a31c6584da082e084affectedgit295ef44a2abaf97d7a594b1d4c60d4be3738191fUnavailableNone listed
8d0347f6c3a9d4953ddd636a31c6584da082e084affectedgit4abda85197ba5d695e6040d580b4b409ce0d3733UnavailableNone listed
8d0347f6c3a9d4953ddd636a31c6584da082e084affectedgitc541dce86c537714b6761a79a969c1623dfa222bUnavailableNone listed

Linux

Vendor
Linux
Product
Linux
Platforms
Unknown
Default status
affected
Linux · Scoped product and version facts
Version (version)Status (status)Version scheme (versionType)Exclusive end (lessThan)Inclusive end (lessThanOrEqual)Status changes (at → status)
5.1affectedUnavailableUnavailableUnavailableNone listed
0unaffectedsemver5.1UnavailableNone listed
5.4.253unaffectedsemverUnavailable5.4.*None listed
5.10.190unaffectedsemverUnavailable5.10.*None listed
5.15.126unaffectedsemverUnavailable5.15.*None listed
6.1.45unaffectedsemverUnavailable6.1.*None listed
6.4.10unaffectedsemverUnavailable6.4.*None listed
6.5unaffectedoriginal_commit_for_fixUnavailable*None listed