Heimdall Security Logo

CVE-2026-68175

Vulnérabilité non évaluée dans Linux (Linux)

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, 7.2, c521efd1700a8c0f7ce26f011f5eaecca17fabfa, <=6.12.*, 6.12.101, <cb459fec4f7b13caf646101ff076e94ef38434d8, 0, <cf5a82bef623b969a609f2b7e392d06dbae34aa6, <=7.1.*, 5.15.216, <f9e6dfe341fb31c95b9655eb6b1db8b3ae090817, <594e1cf3f736779a535873fd5988162d827bfe4f, <=5.10.*, <=6.6.*, 6.18.42, 7.1.6, 6.1.183, <2.6.33, 2.6.33, <=6.18.*, <1d0b59e2b203c02149d8f63607329debe36b3ec5, <=*, <c1d87e724ae55e781b7cc7ccafb34d9e668582b2, <=5.15.*, <7871128ea41217fa6a58bbbcb44cb0d2e9e60966, <581ac13e12e77d6c64f8719083bdf95209308919, 5.10.265, 6.6.148

Description

In the Linux kernel, the following vulnerability has been resolved: tracing: Fix resource leak on mmiotrace trace_pipe close The mmiotrace tracer was added May 12th 2008. At that time, resources created in pipe_open() could not be freed because there was not pipe_close function pointer of the tracer. The pipe_close function pointer was added in December 7th, 2009, but the mmiotrace tracer was not updated. mmio_pipe_open() allocates a header_iter and takes a pci_dev reference when trace_pipe is opened. mmio_close() frees them, but it was only wired to the tracer's .close callback. tracing_release_pipe() invokes .pipe_close, not .close, when the trace_pipe file is released. As a result, closing trace_pipe with the mmiotrace tracer active leaked the header_iter allocation and left a stale pci_dev reference. Set .pipe_close to mmio_close, matching how function_graph wires both callbacks to the same handler. Note, if the trace_pipe is read to completion, it will clean up the resources, but if one were to run: # head -n 1 /sys/kernel/tracing/trace_pipe VERSION 20070824 Over and over again, it would trigger a massive leak.

Gravité et risque d'exploitation

CVE-2026-68175 obtient un score CVSS de 0.0/10, soit une gravité non évalué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.1.*, 7.2, c521efd1700a8c0f7ce26f011f5eaecca17fabfa, <=6.12.*, 6.12.101, <cb459fec4f7b13caf646101ff076e94ef38434d8, 0, <cf5a82bef623b969a609f2b7e392d06dbae34aa6, <=7.1.*, 5.15.216, <f9e6dfe341fb31c95b9655eb6b1db8b3ae090817, <594e1cf3f736779a535873fd5988162d827bfe4f, <=5.10.*, <=6.6.*, 6.18.42, 7.1.6, 6.1.183, <2.6.33, 2.6.33, <=6.18.*, <1d0b59e2b203c02149d8f63607329debe36b3ec5, <=*, <c1d87e724ae55e781b7cc7ccafb34d9e668582b2, <=5.15.*, <7871128ea41217fa6a58bbbcb44cb0d2e9e60966, <581ac13e12e77d6c64f8719083bdf95209308919, 5.10.265, 6.6.148) 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