CVE-2026-68175

UNRATEDCVSS · not yet scoredTrending — 4 sources updated this week
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: —Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0%
EPSS %ILE
10%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 19, 2026

References (8)

Vendor Advisories for CVE-2026-68175(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 15× in last 7d / 21× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-19 17:25 UTCGHSA enrichment
  2. 2026-08-19 17:21 UTCNVD update
  3. 2026-08-19 17:04 UTCEPSS rescore
  4. 2026-08-19 16:55 UTCGHSA enrichment
  5. 2026-08-19 16:43 UTCMITRE cvelistV5
  6. 2026-08-18 13:48 UTCEPSS rescore
  7. 2026-08-17 13:47 UTCEPSS rescore
  8. 2026-08-17 05:40 UTCGHSA enrichment
  9. 2026-08-17 05:26 UTCNVD update
  10. 2026-08-17 05:10 UTCGHSA enrichment
  11. 2026-08-17 05:05 UTCMITRE cvelistV5
  12. 2026-08-16 14:56 UTCEPSS rescore
  13. 2026-08-16 10:46 UTCGHSA enrichment
  14. 2026-08-15 01:30 UTCEPSS rescore
  15. 2026-08-13 22:00 UTCEPSS rescore
  16. 2026-08-13 12:07 UTCEG score recompute
  17. 2026-08-13 12:07 UTCGHSA enrichment
  18. 2026-08-12 13:51 UTCEPSS rescore
  19. 2026-08-10 13:24 UTCNVD update
  20. 2026-08-10 12:20 UTCEG score recompute
  21. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-68175?
CVE-2026-68175 is a publicly disclosed vulnerability published on August 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 pipeclose function pointer of the…
When was CVE-2026-68175 disclosed?
CVE-2026-68175 was first published in the National Vulnerability Database on August 10, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68175 actively exploited?
CVE-2026-68175 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 89.8% of all scored CVEs.
How do I remediate CVE-2026-68175?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68175, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-68175

Explore →

Is Your Infrastructure Affected by CVE-2026-68175?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs