Heimdall Security Logo

CVE-2024-53057

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

CVSS 7.8 · Élevée
EPSS 0.3%
Linux•Linux•Versions : 6.12, <=6.1.*, 6.11.7, <dbe778b08b5101df9e89bc06e0a3a7ecd2f4ef20, 6.1.116, 6.6.60, <=6.11.*, 5.4.285, <e7f9a6f97eb067599a74f3bcb6761976b0ed303e, 0, <2e95c4384438adeaa772caa560244b1a2efef816, <ce691c814bc7a3c30c220ffb5b7422715458fd9b, <=5.10.*, <=6.6.*, 066a3b5b2346febf9a655b444567b7138e3bb939, <9995909615c3431a5304c1210face5f268d24dba, <=5.4.*, <=4.19.*, 4.19.323, 2.6.25, 5.10.229, <2.6.25, <=*, <580b3189c1972aff0f993837567d36392e9d981b, 5.15.171, <=5.15.*, <597cf9748c3477bf61bc35f0634129f56764ad24, <05df1b1dff8f197f1c275b57ccb2ca33021df552

Description

In the Linux kernel, the following vulnerability has been resolved: net/sched: stop qdisc_tree_reduce_backlog on TC_H_ROOT In qdisc_tree_reduce_backlog, Qdiscs with major handle ffff: are assumed to be either root or ingress. This assumption is bogus since it's valid to create egress qdiscs with major handle ffff: Budimir Markovic found that for qdiscs like DRR that maintain an active class list, it will cause a UAF with a dangling class pointer. In 066a3b5b2346, the concern was to avoid iterating over the ingress qdisc since its parent is itself. The proper fix is to stop when parent TC_H_ROOT is reached because the only way to retrieve ingress is when a hierarchy which does not contain a ffff: major handle call into qdisc_lookup with TC_H_MAJ(TC_H_ROOT). In the scenario where major ffff: is an egress qdisc in any of the tree levels, the updates will also propagate to TC_H_ROOT, which then the iteration must stop. net/sched/sch_api.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

Gravité et risque d'exploitation

CVE-2024-53057 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.29 %, ce qui la place devant 20.6 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions 6.12, <=6.1.*, 6.11.7, <dbe778b08b5101df9e89bc06e0a3a7ecd2f4ef20, 6.1.116, 6.6.60, <=6.11.*, 5.4.285, <e7f9a6f97eb067599a74f3bcb6761976b0ed303e, 0, <2e95c4384438adeaa772caa560244b1a2efef816, <ce691c814bc7a3c30c220ffb5b7422715458fd9b, <=5.10.*, <=6.6.*, 066a3b5b2346febf9a655b444567b7138e3bb939, <9995909615c3431a5304c1210face5f268d24dba, <=5.4.*, <=4.19.*, 4.19.323, 2.6.25, 5.10.229, <2.6.25, <=*, <580b3189c1972aff0f993837567d36392e9d981b, 5.15.171, <=5.15.*, <597cf9748c3477bf61bc35f0634129f56764ad24, <05df1b1dff8f197f1c275b57ccb2ca33021df552) 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