CVE-2026-64299

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

CVSS 7.1 · Élevée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, <e5d5f3bd053a5f14787526c9f0f55ef900d43ac6, <=6.12.*, <0a6070839b1ef276d5b05bedfb787743e140fb17, 6.18.39, <56d4c9ab84714eebb285a2fee68aaedf81e3ef15, 0, <=7.1.*, 7.1.4, <4.10, <265f3a690f6c7d69ef7d2ca50b04b4853a211df3, 60f1d5e3bac44b598f67d36062da96c095d2b700, <ebb55902856973906c8bb339a3a34824ed4a5086, 6.1.178, <=5.10.*, <=6.6.*, <ee5b8888d3248618251fb69a2fad92afcb81557e, 4.10, <=6.18.*, 5.15.212, 6.6.145, 5.10.261, <2dad64a97e1df47f5d9ccb17fa319aa348617226, <=*, <=5.15.*, 6.12.96, <35ae19764eabfe9c29029d3b5713c86e6855acdf, 7.2

Description

In the Linux kernel, the following vulnerability has been resolved: tracing: Prevent out-of-bounds read in glob matching String event fields are not necessarily NUL-terminated, so the filter predicate functions (filter_pred_string(), filter_pred_strloc() and filter_pred_strrelloc()) pass the field length to the regex match callbacks, and the length-aware matchers honour it. regex_match_glob() was the exception: it ignored the length and called glob_match(), which scans the string until it hits a NUL byte. Some string fields are not NUL-terminated. One example is the dynamic char array of the xfs_* namespace tracepoints, which is copied without a trailing NUL. For such a field, glob matching reads past the end of the event field, causing a KASAN slab-out-of-bounds read in glob_match(), reached via regex_match_glob() and filter_match_preds() from the xfs_lookup tracepoint. Add a length-bounded glob_match_len() and use it from regex_match_glob() so glob matching always stops at the field boundary. The matching loop is factored into a shared helper so glob_match() keeps its behaviour.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <e5d5f3bd053a5f14787526c9f0f55ef900d43ac6, <=6.12.*, <0a6070839b1ef276d5b05bedfb787743e140fb17, 6.18.39, <56d4c9ab84714eebb285a2fee68aaedf81e3ef15, 0, <=7.1.*, 7.1.4, <4.10, <265f3a690f6c7d69ef7d2ca50b04b4853a211df3, 60f1d5e3bac44b598f67d36062da96c095d2b700, <ebb55902856973906c8bb339a3a34824ed4a5086, 6.1.178, <=5.10.*, <=6.6.*, <ee5b8888d3248618251fb69a2fad92afcb81557e, 4.10, <=6.18.*, 5.15.212, 6.6.145, 5.10.261, <2dad64a97e1df47f5d9ccb17fa319aa348617226, <=*, <=5.15.*, 6.12.96, <35ae19764eabfe9c29029d3b5713c86e6855acdf, 7.2) 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