Heimdall Security Logo

CVE-2023-52699

Vulnérabilité moyenne dans Linux (Linux)

CVSS 5.3 · Moyenne
EPSS 1.0%
Linux•Linux•Versions : 6.9, <=6.1.*, 6.1.86, <13b33feb2ebddc2b1aa607f553566b18a4af1d76, 2.6.12, <53cb1e52c9db618c08335984d1ca80db220ccf09, <1b4fe801b5bedec2b622ddb18e5c9bf26c63d79f, 6.8.6, 0, <a69224223746ab96d43e5db9d22d136827b7e2d3, <674c1c4229e743070e09db63a23442950ff000d1, <2.6.12, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, <=5.10.*, <=6.6.*, 6.6.27, 5.10.215, <fd203d2c671bdee9ab77090ff394d3b71b627927, 5.15.155, <=5.4.*, 4.19.312, <=4.19.*, 5.4.274, <=6.8.*, <f123dc86388cb669c3d6322702dc441abc35c31e, <=*, <=5.15.*, <89e8524135a3902e7563a5a59b7b5ec1bf4904ac

Description

In the Linux kernel, the following vulnerability has been resolved: sysv: don't call sb_bread() with pointers_lock held syzbot is reporting sleep in atomic context in SysV filesystem [1], for sb_bread() is called with rw_spinlock held. A "write_lock(&pointers_lock) => read_lock(&pointers_lock) deadlock" bug and a "sb_bread() with write_lock(&pointers_lock)" bug were introduced by "Replace BKL for chain locking with sysvfs-private rwlock" in Linux 2.5.12. Then, "[PATCH] err1-40: sysvfs locking fix" in Linux 2.6.8 fixed the former bug by moving pointers_lock lock to the callers, but instead introduced a "sb_bread() with read_lock(&pointers_lock)" bug (which made this problem easier to hit). Al Viro suggested that why not to do like get_branch()/get_block()/ find_shared() in Minix filesystem does. And doing like that is almost a revert of "[PATCH] err1-40: sysvfs locking fix" except that get_branch() from with find_shared() is called without write_lock(&pointers_lock).

Gravité et risque d'exploitation

CVE-2023-52699 obtient un score CVSS de 5.3/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.97 %, ce qui la place devant 61.4 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions 6.9, <=6.1.*, 6.1.86, <13b33feb2ebddc2b1aa607f553566b18a4af1d76, 2.6.12, <53cb1e52c9db618c08335984d1ca80db220ccf09, <1b4fe801b5bedec2b622ddb18e5c9bf26c63d79f, 6.8.6, 0, <a69224223746ab96d43e5db9d22d136827b7e2d3, <674c1c4229e743070e09db63a23442950ff000d1, <2.6.12, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, <=5.10.*, <=6.6.*, 6.6.27, 5.10.215, <fd203d2c671bdee9ab77090ff394d3b71b627927, 5.15.155, <=5.4.*, 4.19.312, <=4.19.*, 5.4.274, <=6.8.*, <f123dc86388cb669c3d6322702dc441abc35c31e, <=*, <=5.15.*, <89e8524135a3902e7563a5a59b7b5ec1bf4904ac) 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