Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2023-54099

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

Not scoredEPSS 0.21%
Published
Updated
Reserved
Assigned by
Linux

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/[email protected]/T/

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.21% · top 88% of all CVEs (7 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 8d0347f6c3a9d4953ddd636a31c6584da082e084 – < 0336b42456e485fda1006b5b411e7372e20fbf03
    • affected 8d0347f6c3a9d4953ddd636a31c6584da082e084 – < 7e4e87ec56aa6d008c64eab31b340a7c452b26cc
    • affected 8d0347f6c3a9d4953ddd636a31c6584da082e084 – < 0ccfe21949bc9f706a86ee7351b74375c0745757
    • affected 8d0347f6c3a9d4953ddd636a31c6584da082e084 – < 295ef44a2abaf97d7a594b1d4c60d4be3738191f
    • affected 8d0347f6c3a9d4953ddd636a31c6584da082e084 – < 4abda85197ba5d695e6040d580b4b409ce0d3733
    • affected 8d0347f6c3a9d4953ddd636a31c6584da082e084 – < c541dce86c537714b6761a79a969c1623dfa222b
  • Linux · Linux

    • affected 5.1
    • unaffected < 5.1
    • unaffected 5.4.253 – ≤ 5.4.*
    • unaffected 5.10.190 – ≤ 5.10.*
    • unaffected 5.15.126 – ≤ 5.15.*
    • unaffected 6.1.45 – ≤ 6.1.*
    • unaffected 6.4.10 – ≤ 6.4.*
    • unaffected 6.5 – ≤ *

References (6)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2023-54099 badge
[![CVE-2023-54099](https://trackcve.app/badge/CVE-2023-54099.svg)](https://trackcve.app/cve/CVE-2023-54099)

Record last updated .