Answer in brief
CVE-2026-68175 records a Unknown severity vulnerability in tracing: Fix resource leak on mmiotrace trace_pipe close. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=c521efd1700a8c0f7ce26f011f5eaecca17fabfa <f9e6dfe341fb31c95b9655eb6b1db8b3ae090817 || >=c521efd1700a8c0f7ce26f011f5eaecca17fabfa <594e1cf3f736779a535873fd5988162d827bfe4f || >=c521efd1700a8c0f7ce26f011f5eaecca17fabfa <cf5a82bef623b969a609f2b7e392d06dbae34aa6 || >=c521efd1700a8c0f7ce26f011f5eaecca17fabfa <cb459fec4f7b13caf646101ff076e94ef38434d8 || >=c521efd1700a8c0f7ce26f011f5eaecca17fabfa <c1d87e724ae55e781b7cc7ccafb34d9e668582b2 | f9e6dfe341fb31c95b9655eb6b1db8b3ae090817, 594e1cf3f736779a535873fd5988162d827bfe4f, cf5a82bef623b969a609f2b7e392d06dbae34aa6, cb459fec4f7b13caf646101ff076e94ef38434d8, c1d87e724ae55e781b7cc7ccafb34d9e668582b2 |
| Linux/Linuxgeneric | 2.6.33 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-68175 records a Unknown severity vulnerability in tracing: Fix resource leak on mmiotrace trace_pipe close. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=c521efd1700a8c0f7ce26f011f5eaecca17fabfa <f9e6dfe341fb31c95b9655eb6b1db8b3ae090817 || >=c521efd1700a8c0f7ce26f011f5eaecca17fabfa <594e1cf3f736779a535873fd5988162d827bfe4f || >=c521efd1700a8c0f7ce26f011f5eaecca17fabfa <cf5a82bef623b969a609f2b7e392d06dbae34aa6 || >=c521efd1700a8c0f7ce26f011f5eaecca17fabfa <cb459fec4f7b13caf646101ff076e94ef38434d8 || >=c521efd1700a8c0f7ce26f011f5eaecca17fabfa <c1d87e724ae55e781b7cc7ccafb34d9e668582b2 | f9e6dfe341fb31c95b9655eb6b1db8b3ae090817, 594e1cf3f736779a535873fd5988162d827bfe4f, cf5a82bef623b969a609f2b7e392d06dbae34aa6, cb459fec4f7b13caf646101ff076e94ef38434d8, c1d87e724ae55e781b7cc7ccafb34d9e668582b2 |
| Linux/Linuxgeneric | 2.6.33 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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.
Quoted source text, attributed separately from HOL analysis.