CVE-2026-90013

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

CVSS 7.8 · Élevée
EPSS 0.2%
Linux•Linux•Versions : 577b785f55168d5acb3d123ba41bfe8d7981e044, <f2951ebd15c36a1ea4820a7f0cbb0b5f1c028b73, 6.18.52, <=*, <=6.12.*, <2.6.30, <64a41f4a9a968f54f3792399aa4d2a9fdb23b0a5, 6.12.112, <=6.18.*, <=7.2.*, 2.6.30, 7.3, 0, 7.2.5, <d0f37d77b9b4b241e0b30ef2562f6353cbda3bec, <97ceaffbd672449ad7ead5ae8788dce16374b0c1

Description

In the Linux kernel, the following vulnerability has been resolved: tracing: Take trace_array reference when opening options file The options files do not take the trace_array reference for the options they represent. This could cause a use-after-free kernel crash if one of these files is opened by one task and another task removes the instance that the option is for. Because it doesn't take a reference upon opening, it will not stop the removal which will free the options descriptor that is being used. As the options are somewhat dynamic in their creation at boot up, each file represents a flag in the trace_array. The trace_array has an array of indexes to represent each of these flags that is stored in the trace_flags_index array. The address of the index array element is used to pass to the inode->i_private pointer. Then that element is read which holds the index (which represents the flag) and then the index is used to calculate the trace_array descriptor from its trace_flags_index array. One issue is that the index element can not be referenced until the trace_array's reference is taken. To handle this, create a new helper function called: trace_array_options_get() that will iterate all the existing trace_arrays in the ftrace_trace_arrays list (under the trace_types_lock), and compare the passed in address of the index element with the entire array of the trace_array's trace_flags_index array. If it matches, then up the corresponding trace_array's reference and return.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions 577b785f55168d5acb3d123ba41bfe8d7981e044, <f2951ebd15c36a1ea4820a7f0cbb0b5f1c028b73, 6.18.52, <=*, <=6.12.*, <2.6.30, <64a41f4a9a968f54f3792399aa4d2a9fdb23b0a5, 6.12.112, <=6.18.*, <=7.2.*, 2.6.30, 7.3, 0, 7.2.5, <d0f37d77b9b4b241e0b30ef2562f6353cbda3bec, <97ceaffbd672449ad7ead5ae8788dce16374b0c1) 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