Heimdall Security Logo

CVE-2023-53337

Vulnérabilité moyenne dans Linux (Linux)

CVSS 5.5 · Moyenne
EPSS 0.2%
Linux•Linux•Versions : 5.10.180, <=6.1.*, 6.2.15, <a73201c607d8e506358d60aafddda4246bdd9350, 5.15.111, 0, 8c26c4e2694a163d525976e804d81cd955bbb40c, <13f73ef77baa4764dc1ca4fcbae9cade05b83866, <=6.3.*, <7c3e662048053802f6b0db3a78e97f4e1f7edc4f, 6.4, 4.14.315, <28a65b49eb53e172d23567005465019658bfdb4d, <3.10, <=5.10.*, <=4.14.*, <55f7810632f993cff622a0ddbc7c865892294b61, <=5.4.*, 4.19.283, <=4.19.*, <=6.2.*, <bd89073fc7a5d03b1d06b372addbe405e5a925f4, 6.1.28, <=*, <4569a292a84e340e97d178898ad1cfe1a3080a61, <=5.15.*, 3.10, <e9c5412c5972124776c1b873533eb39e287a4dfa, <4005cec6847c06ee191583270b7cdd7e696543cc, 5.4.243, 6.3.2

Description

In the Linux kernel, the following vulnerability has been resolved: nilfs2: do not write dirty data after degenerating to read-only According to syzbot's report, mark_buffer_dirty() called from nilfs_segctor_do_construct() outputs a warning with some patterns after nilfs2 detects metadata corruption and degrades to read-only mode. After such read-only degeneration, page cache data may be cleared through nilfs_clear_dirty_page() which may also clear the uptodate flag for their buffer heads. However, even after the degeneration, log writes are still performed by unmount processing etc., which causes mark_buffer_dirty() to be called for buffer heads without the "uptodate" flag and causes the warning. Since any writes should not be done to a read-only file system in the first place, this fixes the warning in mark_buffer_dirty() by letting nilfs_segctor_do_construct() abort early if in read-only mode. This also changes the retry check of nilfs_segctor_write_out() to avoid unnecessary log write retries if it detects -EROFS that nilfs_segctor_do_construct() returned.

Gravité et risque d'exploitation

CVE-2023-53337 obtient un score CVSS de 5.5/10, soit une gravité moyenne. 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 10.2 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions 5.10.180, <=6.1.*, 6.2.15, <a73201c607d8e506358d60aafddda4246bdd9350, 5.15.111, 0, 8c26c4e2694a163d525976e804d81cd955bbb40c, <13f73ef77baa4764dc1ca4fcbae9cade05b83866, <=6.3.*, <7c3e662048053802f6b0db3a78e97f4e1f7edc4f, 6.4, 4.14.315, <28a65b49eb53e172d23567005465019658bfdb4d, <3.10, <=5.10.*, <=4.14.*, <55f7810632f993cff622a0ddbc7c865892294b61, <=5.4.*, 4.19.283, <=4.19.*, <=6.2.*, <bd89073fc7a5d03b1d06b372addbe405e5a925f4, 6.1.28, <=*, <4569a292a84e340e97d178898ad1cfe1a3080a61, <=5.15.*, 3.10, <e9c5412c5972124776c1b873533eb39e287a4dfa, <4005cec6847c06ee191583270b7cdd7e696543cc, 5.4.243, 6.3.2) 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