Heimdall Security Logo

CVE-2023-53810

Vulnérabilité élevée dans Linux (Linux)

CVSS 7.8 · Élevée
EPSS 0.1%
Linux•Linux•Versions : 5.10.180, <=6.1.*, 6.2.15, 5.15.111, 0, <92d5d233b9ff531cf9cc36ab4251779e07adb633, <9cd1e566676bbcb8a126acd921e4e194e6339603, <5.8, <=6.3.*, 6.4, <=5.10.*, <b278570e2c59d538216f8b656e97680188a8fba4, <=6.2.*, <d206f79d9cd658665b37ce8134c6ec849ac7af0c, <7d206ec7a04e8545828191b6ea8b49d3ea61391f, a892c8d52c02284076fbbacae6692aa5c5807d11, 6.1.28, <=*, <=5.15.*, 5.8, <874bdf43b4a7dc5463c31508f62b3e42eb237b08, 6.3.2

Description

In the Linux kernel, the following vulnerability has been resolved: blk-mq: release crypto keyslot before reporting I/O complete Once all I/O using a blk_crypto_key has completed, filesystems can call blk_crypto_evict_key(). However, the block layer currently doesn't call blk_crypto_put_keyslot() until the request is being freed, which happens after upper layers have been told (via bio_endio()) the I/O has completed. This causes a race condition where blk_crypto_evict_key() can see 'slot_refs != 0' without there being an actual bug. This makes __blk_crypto_evict_key() hit the 'WARN_ON_ONCE(atomic_read(&slot->slot_refs) != 0)' and return without doing anything, eventually causing a use-after-free in blk_crypto_reprogram_all_keys(). (This is a very rare bug and has only been seen when per-file keys are being used with fscrypt.) There are two options to fix this: either release the keyslot before bio_endio() is called on the request's last bio, or make __blk_crypto_evict_key() ignore slot_refs. Let's go with the first solution, since it preserves the ability to report bugs (via WARN_ON_ONCE) where a key is evicted while still in-use.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions 5.10.180, <=6.1.*, 6.2.15, 5.15.111, 0, <92d5d233b9ff531cf9cc36ab4251779e07adb633, <9cd1e566676bbcb8a126acd921e4e194e6339603, <5.8, <=6.3.*, 6.4, <=5.10.*, <b278570e2c59d538216f8b656e97680188a8fba4, <=6.2.*, <d206f79d9cd658665b37ce8134c6ec849ac7af0c, <7d206ec7a04e8545828191b6ea8b49d3ea61391f, a892c8d52c02284076fbbacae6692aa5c5807d11, 6.1.28, <=*, <=5.15.*, 5.8, <874bdf43b4a7dc5463c31508f62b3e42eb237b08, 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