Heimdall Security Logo

CVE-2023-53461

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

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, 0, <b50d6e06cca7b67a3d73ca660dda27662b76e6ea, 2b188cc1bb857a9d4701ae59aa7768b5124e262e, <8e29835366138389bfad3b31ea06960d0a77bf77, 5.15.121, 6.5, <4826c59453b3b4677d6bf72814e7ababdea86949, <=5.10.*, <28e649dc9947e6525c95e32aa9a8e147925e3f56, <5.1, 5.1, 6.4.4, <=*, <=5.15.*, <58e80cb68b057e974768792c34708c6957810486, 5.10.188, <=6.4.*, 6.1.39

Description

In the Linux kernel, the following vulnerability has been resolved: io_uring: wait interruptibly for request completions on exit WHen the ring exits, cleanup is done and the final cancelation and waiting on completions is done by io_ring_exit_work. That function is invoked by kworker, which doesn't take any signals. Because of that, it doesn't really matter if we wait for completions in TASK_INTERRUPTIBLE or TASK_UNINTERRUPTIBLE state. However, it does matter to the hung task detection checker! Normally we expect cancelations and completions to happen rather quickly. Some test cases, however, will exit the ring and park the owning task stopped (eg via SIGSTOP). If the owning task needs to run task_work to complete requests, then io_ring_exit_work won't make any progress until the task is runnable again. Hence io_ring_exit_work can trigger the hung task detection, which is particularly problematic if panic-on-hung-task is enabled. As the ring exit doesn't take signals to begin with, have it wait interruptibly rather than uninterruptibly. io_uring has a separate stuck-exit warning that triggers independently anyway, so we're not really missing anything by making this switch.

Gravité et risque d'exploitation

CVE-2023-53461 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.15 %, ce qui la place devant 4.3 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, 0, <b50d6e06cca7b67a3d73ca660dda27662b76e6ea, 2b188cc1bb857a9d4701ae59aa7768b5124e262e, <8e29835366138389bfad3b31ea06960d0a77bf77, 5.15.121, 6.5, <4826c59453b3b4677d6bf72814e7ababdea86949, <=5.10.*, <28e649dc9947e6525c95e32aa9a8e147925e3f56, <5.1, 5.1, 6.4.4, <=*, <=5.15.*, <58e80cb68b057e974768792c34708c6957810486, 5.10.188, <=6.4.*, 6.1.39) 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