Heimdall Security Logo

CVE-2026-23047

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

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : 922dab6134178cae317ae00de86376cba59f3147, <=6.1.*, <=6.12.*, <6f468f6ff233c6a81e0e761d9124e982903fe9a5, <5d0dc83cb9a69c1d0bea58f1c430199b05f6b021, 0, <2b3329b3c29d9e188e40d902d5230c2d5989b940, <4d3399c52e0e61720ae898f5a0b5b75d4460ae24, 6.1.161, 5.15.198, <=5.10.*, <=6.6.*, 6.18.6, <c0fe2994f9a9d0a2ec9e42441ea5ba74b6a16176, <5647d42c47b535573b63e073e91164d6a5bb058c, 4.7, <=6.18.*, 5.10.248, <=*, 6.12.66, <=5.15.*, <4.7, 6.19, <4ebc711b738d139cabe2fc9e7e7749847676a342, 6.6.121

Description

In the Linux kernel, the following vulnerability has been resolved: libceph: make calc_target() set t->paused, not just clear it Currently calc_target() clears t->paused if the request shouldn't be paused anymore, but doesn't ever set t->paused even though it's able to determine when the request should be paused. Setting t->paused is left to __submit_request() which is fine for regular requests but doesn't work for linger requests -- since __submit_request() doesn't operate on linger requests, there is nowhere for lreq->t.paused to be set. One consequence of this is that watches don't get reestablished on paused -> unpaused transitions in cases where requests have been paused long enough for the (paused) unwatch request to time out and for the subsequent (re)watch request to enter the paused state. On top of the watch not getting reestablished, rbd_reregister_watch() gets stuck with rbd_dev->watch_mutex held: rbd_register_watch __rbd_register_watch ceph_osdc_watch linger_reg_commit_wait It's waiting for lreq->reg_commit_wait to be completed, but for that to happen the respective request needs to end up on need_resend_linger list and be kicked when requests are unpaused. There is no chance for that if the request in question is never marked paused in the first place. The fact that rbd_dev->watch_mutex remains taken out forever then prevents the image from getting unmapped -- "rbd unmap" would inevitably hang in D state on an attempt to grab the mutex.

Gravité et risque d'exploitation

CVE-2026-23047 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.19 %, ce qui la place devant 8.0 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions 922dab6134178cae317ae00de86376cba59f3147, <=6.1.*, <=6.12.*, <6f468f6ff233c6a81e0e761d9124e982903fe9a5, <5d0dc83cb9a69c1d0bea58f1c430199b05f6b021, 0, <2b3329b3c29d9e188e40d902d5230c2d5989b940, <4d3399c52e0e61720ae898f5a0b5b75d4460ae24, 6.1.161, 5.15.198, <=5.10.*, <=6.6.*, 6.18.6, <c0fe2994f9a9d0a2ec9e42441ea5ba74b6a16176, <5647d42c47b535573b63e073e91164d6a5bb058c, 4.7, <=6.18.*, 5.10.248, <=*, 6.12.66, <=5.15.*, <4.7, 6.19, <4ebc711b738d139cabe2fc9e7e7749847676a342, 6.6.121) 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