CVE-2026-68175tracing: Fix resource leak on mmiotrace trace_pipe close
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- Not yet scored
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Aug 19, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from c521efd1700a8c0f7ce26f011f5eaecca17fabfa before 7871128ea41217fa6a58bbbcb44cb0d2e9e60966; from c521efd1700a8c0f7ce26f011f5eaecca17fabfa before 1d0b59e2b203c02149d8f63607329debe36b3ec5; from c521efd1700a8c0f7ce26f011f5eaecca17fabfa before 581ac13e12e77d6c64f8719083bdf95209308919; from c521efd1700a8c0f7ce26f011f5eaecca17fabfa before f9e6dfe341fb31c95b9655eb6b1db8b3ae090817; from c521efd1700a8c0f7ce26f011f5eaecca17fabfa before 594e1cf3f736779a535873fd5988162d827bfe4f; from c521efd1700a8c0f7ce26f011f5eaecca17fabfa before cf5a82bef623b969a609f2b7e392d06dbae34aa6; from c521efd1700a8c0f7ce26f011f5eaecca17fabfa before cb459fec4f7b13caf646101ff076e94ef38434d8; from c521efd1700a8c0f7ce26f011f5eaecca17fabfa before c1d87e724ae55e781b7cc7ccafb34d9e668582b2 | CNA record |
References
- https://git.kernel.org/stable/c/7871128ea41217fa6a58bbbcb44cb0d2e9e60966
- https://git.kernel.org/stable/c/1d0b59e2b203c02149d8f63607329debe36b3ec5
- https://git.kernel.org/stable/c/581ac13e12e77d6c64f8719083bdf95209308919
- https://git.kernel.org/stable/c/f9e6dfe341fb31c95b9655eb6b1db8b3ae090817
- https://git.kernel.org/stable/c/594e1cf3f736779a535873fd5988162d827bfe4f
- https://git.kernel.org/stable/c/cf5a82bef623b969a609f2b7e392d06dbae34aa6
- https://git.kernel.org/stable/c/cb459fec4f7b13caf646101ff076e94ef38434d8
- https://git.kernel.org/stable/c/c1d87e724ae55e781b7cc7ccafb34d9e668582b2
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.