CVE-2025-71109

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

CVSS 7.1 · Élevée
EPSS 0.2%
Linux•Linux•Versions : 6.12.64, <36dac9a3dda1f2bae343191bc16b910c603cac25, <=*, <=6.12.*, 6.19, <=6.18.*, <2.6.35, 0, 6.18.3, e424054000878d7eb11e44289242886d6e219d22, <7f39b9d0e86ed6236b9a5fb67616ab1f76c4f150, 2.6.35, <e3e33ac2eb69d595079a1a1e444c2fb98efdd42d

Description

In the Linux kernel, the following vulnerability has been resolved: MIPS: ftrace: Fix memory corruption when kernel is located beyond 32 bits Since commit e424054000878 ("MIPS: Tracing: Reduce the overhead of dynamic Function Tracer"), the macro UASM_i_LA_mostly has been used, and this macro can generate more than 2 instructions. At the same time, the code in ftrace assumes that no more than 2 instructions can be generated, which is why it stores them in an int[2] array. However, as previously noted, the macro UASM_i_LA_mostly (and now UASM_i_LA) causes a buffer overflow when _mcount is beyond 32 bits. This leads to corruption of the variables located in the __read_mostly section. This corruption was observed because the variable __cpu_primary_thread_mask was corrupted, causing a hang very early during boot. This fix prevents the corruption by avoiding the generation of instructions if they could exceed 2 instructions in length. Fortunately, insn_la_mcount is only used if the instrumented code is located outside the kernel code section, so dynamic ftrace can still be used, albeit in a more limited scope. This is still preferable to corrupting memory and/or crashing the kernel.

Gravité et risque d'exploitation

CVE-2025-71109 obtient un score CVSS de 7.1/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.21 %, ce qui la place devant 10.6 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions 6.12.64, <36dac9a3dda1f2bae343191bc16b910c603cac25, <=*, <=6.12.*, 6.19, <=6.18.*, <2.6.35, 0, 6.18.3, e424054000878d7eb11e44289242886d6e219d22, <7f39b9d0e86ed6236b9a5fb67616ab1f76c4f150, 2.6.35, <e3e33ac2eb69d595079a1a1e444c2fb98efdd42d) 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