CVE-2026-53011

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

CVSS 7.8 · Élevée
EPSS 0.1%
Linux•Linux•Versions : <=6.1.*, <=7.0.*, <=6.12.*, <0e62171df8ed4804d00db088f17eed06468233fa, 5.2, 0, 6.18.33, <3471874578160a28c171a607fa069f24062634b8, <105425b1969c5affe532713cfac1c0b320d7ac2b, 5.15.209, 6.12.91, <=5.10.*, <=6.6.*, 6.1.175, <7256996e1ef553716817f3bfd077c2f3b48b582f, 6.6.141, 7.1, <=6.18.*, 7.0.10, <1bd286fa3e21200133478ed523cc6a2788baf38a, 5.10.258, <b73235da5dde77ed1264f9767b62c28c9d71fd78, <a8fc396519ef4f081bc545e88f61241728bb78d7, <=*, <eee072fe16c646190d33ae69c9983d8de1562bf8, <=5.15.*, <5.2, a3d43c0d56f1b94e74963a2fbadfb70126d92213

Description

In the Linux kernel, the following vulnerability has been resolved: net/sched: taprio: fix use-after-free in advance_sched() on schedule switch In advance_sched(), when should_change_schedules() returns true, switch_schedules() is called to promote the admin schedule to oper. switch_schedules() queues the old oper schedule for RCU freeing via call_rcu(), but 'next' still points into an entry of the old oper schedule. The subsequent 'next->end_time = end_time' and rcu_assign_pointer(q->current_entry, next) are use-after-free. Fix this by selecting 'next' from the new oper schedule immediately after switch_schedules(), and using its pre-calculated end_time. setup_first_end_time() sets the first entry's end_time to base_time + interval when the schedule is installed, so the value is already correct. The deleted 'end_time = sched_base_time(admin)' assignment was also harmful independently: it would overwrite the new first entry's pre-calculated end_time with just base_time.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=7.0.*, <=6.12.*, <0e62171df8ed4804d00db088f17eed06468233fa, 5.2, 0, 6.18.33, <3471874578160a28c171a607fa069f24062634b8, <105425b1969c5affe532713cfac1c0b320d7ac2b, 5.15.209, 6.12.91, <=5.10.*, <=6.6.*, 6.1.175, <7256996e1ef553716817f3bfd077c2f3b48b582f, 6.6.141, 7.1, <=6.18.*, 7.0.10, <1bd286fa3e21200133478ed523cc6a2788baf38a, 5.10.258, <b73235da5dde77ed1264f9767b62c28c9d71fd78, <a8fc396519ef4f081bc545e88f61241728bb78d7, <=*, <eee072fe16c646190d33ae69c9983d8de1562bf8, <=5.15.*, <5.2, a3d43c0d56f1b94e74963a2fbadfb70126d92213) 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