Heimdall Security Logo

CVE-2023-54099

Vulnérabilité non évaluée dans Linux (Linux)

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, 5.10.190, <7e4e87ec56aa6d008c64eab31b340a7c452b26cc, <295ef44a2abaf97d7a594b1d4c60d4be3738191f, 0, <0336b42456e485fda1006b5b411e7372e20fbf03, 6.5, <=5.10.*, 5.15.126, <0ccfe21949bc9f706a86ee7351b74375c0745757, <5.1, <=5.4.*, <c541dce86c537714b6761a79a969c1623dfa222b, 6.4.10, 5.4.253, 5.1, <4abda85197ba5d695e6040d580b4b409ce0d3733, <=*, 6.1.45, <=5.15.*, 8d0347f6c3a9d4953ddd636a31c6584da082e084, <=6.4.*

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/

Gravité et risque d'exploitation

CVE-2023-54099 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.21 %, ce qui la place devant 11.1 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, 5.10.190, <7e4e87ec56aa6d008c64eab31b340a7c452b26cc, <295ef44a2abaf97d7a594b1d4c60d4be3738191f, 0, <0336b42456e485fda1006b5b411e7372e20fbf03, 6.5, <=5.10.*, 5.15.126, <0ccfe21949bc9f706a86ee7351b74375c0745757, <5.1, <=5.4.*, <c541dce86c537714b6761a79a969c1623dfa222b, 6.4.10, 5.4.253, 5.1, <4abda85197ba5d695e6040d580b4b409ce0d3733, <=*, 6.1.45, <=5.15.*, 8d0347f6c3a9d4953ddd636a31c6584da082e084, <=6.4.*) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références

Rechercher une autre CVE