Heimdall Security Logo

CVE-2025-38377

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

CVSS 8.8 · Élevée
EPSS 0.3%
Linux•Linux•Versions : <=6.1.*, <=6.12.*, 2.6.12, <b6b232e16e08c6dc120672b4753392df0d28c1b4, 0, 5.15.187, 6.6.97, <34a500caf48c47d5171f4aa1f237da39b07c6157, 6.1.144, <=6.15.*, <2.6.12, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 6.15.6, <=5.10.*, <=6.6.*, 5.10.240, 5.4.296, <fe62a35fb1f77f494ed534fc69a9043dc5a30ce1, <=5.4.*, 6.16, <2b952dbb32fef835756f07ff0cd77efbb836dfea, <94e0918e39039c47ddceb609500817f7266be756, 6.12.37, <7a1841c9609377e989ec41c16551309ce79c39e4, <=*, <446ac00b86be1670838e513b643933d78837d8db, <=5.15.*, <2c6c82ee074bfcfd1bc978ec45bfea37703d840a

Description

In the Linux kernel, the following vulnerability has been resolved: rose: fix dangling neighbour pointers in rose_rt_device_down() There are two bugs in rose_rt_device_down() that can cause use-after-free: 1. The loop bound `t->count` is modified within the loop, which can cause the loop to terminate early and miss some entries. 2. When removing an entry from the neighbour array, the subsequent entries are moved up to fill the gap, but the loop index `i` is still incremented, causing the next entry to be skipped. For example, if a node has three neighbours (A, A, B) with count=3 and A is being removed, the second A is not checked. i=0: (A, A, B) -> (A, B) with count=2 ^ checked i=1: (A, B) -> (A, B) with count=2 ^ checked (B, not A!) i=2: (doesn't occur because i < count is false) This leaves the second A in the array with count=2, but the rose_neigh structure has been freed. Code that accesses these entries assumes that the first `count` entries are valid pointers, causing a use-after-free when it accesses the dangling pointer. Fix both issues by iterating over the array in reverse order with a fixed loop bound. This ensures that all entries are examined and that the removal of an entry doesn't affect subsequent iterations.

Gravité et risque d'exploitation

CVE-2025-38377 obtient un score CVSS de 8.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.26 %, ce qui la place devant 16.9 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=6.12.*, 2.6.12, <b6b232e16e08c6dc120672b4753392df0d28c1b4, 0, 5.15.187, 6.6.97, <34a500caf48c47d5171f4aa1f237da39b07c6157, 6.1.144, <=6.15.*, <2.6.12, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 6.15.6, <=5.10.*, <=6.6.*, 5.10.240, 5.4.296, <fe62a35fb1f77f494ed534fc69a9043dc5a30ce1, <=5.4.*, 6.16, <2b952dbb32fef835756f07ff0cd77efbb836dfea, <94e0918e39039c47ddceb609500817f7266be756, 6.12.37, <7a1841c9609377e989ec41c16551309ce79c39e4, <=*, <446ac00b86be1670838e513b643933d78837d8db, <=5.15.*, <2c6c82ee074bfcfd1bc978ec45bfea37703d840a) 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