CVE-2026-68175

tracing: Fix resource leak on mmiotrace trace_pipe close

N/A
Published: August 10, 2026 at 11:59 AM UTC
Updated: August 19, 2026 at 05:20 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.33 ≤ v < 5.10.2652.6.33 ≤ v < 5.15.2162.6.33 ≤ v < 6.1.1832.6.33 ≤ v < 6.12.1012.6.33 ≤ v < 6.18.422.6.33 ≤ v < 6.6.1482.6.33 ≤ v < 7.1.62.6.33 ≤ v < 7.22.6.33c521efd1700a8c0f7ce26f011f5eaecca17fabfa
Vendor states this is fixed in 1d0b59e2b203c02149d8f63607329debe36b3ec5 (fixed)
Vendor states this is fixed in 581ac13e12e77d6c64f8719083bdf95209308919 (fixed)
Vendor states this is fixed in 594e1cf3f736779a535873fd5988162d827bfe4f (fixed)
Vendor states this is fixed in 7871128ea41217fa6a58bbbcb44cb0d2e9e60966 (fixed)
Vendor states this is fixed in c1d87e724ae55e781b7cc7ccafb34d9e668582b2 (fixed)
Vendor states this is fixed in cb459fec4f7b13caf646101ff076e94ef38434d8 (fixed)
Vendor states this is fixed in cf5a82bef623b969a609f2b7e392d06dbae34aa6 (fixed)
Vendor states this is fixed in f9e6dfe341fb31c95b9655eb6b1db8b3ae090817 (fixed)
Vendor states this is fixed in 2.6.33 (unaffected)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.101 (unaffected)
Vendor states this is fixed in 6.18.42 (unaffected)
Vendor states this is fixed in 6.6.148 (unaffected)
Vendor states this is fixed in 7.1.6 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card