CVE-2026-68175

published 10 Aug 2026 · updated 19 Aug 2026

tracing: Fix resource leak on mmiotrace trace_pipe close

5.5MediumCVSS 5.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 1d0b59e2b203c02149d8f63607329debe36b3ec5, Kernel 581ac13e12e77d6c64f8719083bdf95209308919, Kernel 594e1cf3f736779a535873fd5988162d827bfe4f and 5 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=2.6.33, >=c521efd1700a8c0f7ce26f011f5eaecca17fabfa <1d0b59e2b203c02149d8f63607329debe36b3ec5, >=c521efd1700a8c0f7ce26f011f5eaecca17fabfa <581ac13e12e77d6c64f8719083bdf95209308919, >=c521efd1700a8c0f7ce26f011f5eaecca17fabfa <594e1cf3f736779a535873fd5988162d827bfe4f, >=c521efd1700a8c0f7ce26f011f5eaecca17fabfa <7871128ea41217fa6a58bbbcb44cb0d2e9e60966, >=c521efd1700a8c0f7ce26f011f5eaecca17fabfa <c1d87e724ae55e781b7cc7ccafb34d9e668582b2, >=c521efd1700a8c0f7ce26f011f5eaecca17fabfa <cb459fec4f7b13caf646101ff076e94ef38434d8, >=c521efd1700a8c0f7ce26f011f5eaecca17fabfa <cf5a82bef623b969a609f2b7e392d06dbae34aa6, >=c521efd1700a8c0f7ce26f011f5eaecca17fabfa <f9e6dfe341fb31c95b9655eb6b1db8b3ae0908171d0b59e2b203c02149d8f63607329debe36b3ec5, 581ac13e12e77d6c64f8719083bdf95209308919, 594e1cf3f736779a535873fd5988162d827bfe4f, 7871128ea41217fa6a58bbbcb44cb0d2e9e60966, c1d87e724ae55e781b7cc7ccafb34d9e668582b2, cb459fec4f7b13caf646101ff076e94ef38434d8, cf5a82bef623b969a609f2b7e392d06dbae34aa6, f9e6dfe341fb31c95b9655eb6b1db8b3ae090817

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-68175 severity on Zeptric[![CVE-2026-68175](https://zeptric.io/badge/cve/CVE-2026-68175.svg)](https://zeptric.io/cve/CVE-2026-68175)