CVE-2026-68175: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-frw4-mrvx-h68w
Share
Published
Advisory Summary

CVE-2026-68175 is a security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.

CVE-2026-68175 at a Glance

CVE Identifier CVE-2026-68175
GHSA Identifier GHSA-frw4-mrvx-h68w
Severity N/A
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

How to Fix CVE-2026-68175

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-68175, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

References

NVD — CVE-2026-68175 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-68175
git.kernel.org/stable/c/1d0b59e2b2... WEB
https://git.kernel.org/stable/c/1d0b59e2b203c02149d8f63607329debe36b3ec5
git.kernel.org/stable/c/581ac13e12... WEB
https://git.kernel.org/stable/c/581ac13e12e77d6c64f8719083bdf95209308919
git.kernel.org/stable/c/594e1cf3f7... WEB
https://git.kernel.org/stable/c/594e1cf3f736779a535873fd5988162d827bfe4f
git.kernel.org/stable/c/7871128ea4... WEB
https://git.kernel.org/stable/c/7871128ea41217fa6a58bbbcb44cb0d2e9e60966
git.kernel.org/stable/c/c1d87e724a... WEB
https://git.kernel.org/stable/c/c1d87e724ae55e781b7cc7ccafb34d9e668582b2
git.kernel.org/stable/c/cb459fec4f... WEB
https://git.kernel.org/stable/c/cb459fec4f7b13caf646101ff076e94ef38434d8
git.kernel.org/stable/c/cf5a82bef6... WEB
https://git.kernel.org/stable/c/cf5a82bef623b969a609f2b7e392d06dbae34aa6
git.kernel.org/stable/c/f9e6dfe341... WEB
https://git.kernel.org/stable/c/f9e6dfe341fb31c95b9655eb6b1db8b3ae090817

Frequently Asked Questions

What is CVE-2026-68175?
CVE-2026-68175 is a security vulnerability in Software classified as a security vulnerability vulnerability under General Security Weakness.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-68175?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-68175?
CVE-2026-68175 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-68175?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-frw4-mrvx-h68w",
  "modified" : "2026-08-19T18:32:08Z",
  "published" : "2026-08-10T15:33:39Z",
  "aliases" : [ "CVE-2026-68175" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Fix resource leak on mmiotrace trace_pipe close\n\nThe mmiotrace tracer was added May 12th 2008. At that time, resources\ncreated in pipe_open() could not be freed because there was not\npipe_close function pointer of the tracer. The pipe_close function pointer\nwas added in December 7th, 2009, but the mmiotrace tracer was not updated.\n\nmmio_pipe_open() allocates a header_iter and takes a pci_dev reference\nwhen trace_pipe is opened. mmio_close() frees them, but it was only\nwired to the tracer's .close callback.\n\ntracing_release_pipe() invokes .pipe_close, not .close, when the\ntrace_pipe file is released. As a result, closing trace_pipe with the\nmmiotrace tracer active leaked the header_iter allocation and left a\nstale pci_dev reference.\n\nSet .pipe_close to mmio_close, matching how function_graph wires both\ncallbacks to the same handler.\n\nNote, if the trace_pipe is read to completion, it will clean up the\nresources, but if one were to run:\n\n  # head -n 1 /sys/kernel/tracing/trace_pipe\n VERSION 20070824\n\nOver and over again, it would trigger a massive leak.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-68175"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1d0b59e2b203c02149d8f63607329debe36b3ec5"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/581ac13e12e77d6c64f8719083bdf95209308919"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/594e1cf3f736779a535873fd5988162d827bfe4f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/7871128ea41217fa6a58bbbcb44cb0d2e9e60966"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c1d87e724ae55e781b7cc7ccafb34d9e668582b2"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/cb459fec4f7b13caf646101ff076e94ef38434d8"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/cf5a82bef623b969a609f2b7e392d06dbae34aa6"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f9e6dfe341fb31c95b9655eb6b1db8b3ae090817"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-10T13:20:04Z"
  }
}