Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-68175: tracing: Fix resource leak on mmiotrace trace_pipe close

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
  • Fixed version: Linux Linux 1d0b59e2b203c02149d8f63607329debe36b3ec5, 581ac13e12e77d6c64f8719083bdf95209308919, 594e1cf3f736779a535873fd5988162d827bfe4f; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 1d0b59e2b203c02149d8f63607329debe36b3ec5, 581ac13e12e77d6c64f8719083bdf95209308919, 594e1cf3f736779a535873fd5988162d827bfe4f; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Aug 10, 2026
Updated
Aug 19, 2026
EPSS
0.2% · 11th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-68175

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 2.6.33affected
    • c521efd1700a8c0f7ce26f011f5eaecca17fabfa and later · before 7871128ea41217fa6a58bbbcb44cb0d2e9e60966affected · git
    • c521efd1700a8c0f7ce26f011f5eaecca17fabfa and later · before 1d0b59e2b203c02149d8f63607329debe36b3ec5affected · git
    • c521efd1700a8c0f7ce26f011f5eaecca17fabfa and later · before 581ac13e12e77d6c64f8719083bdf95209308919affected · git
    • c521efd1700a8c0f7ce26f011f5eaecca17fabfa and later · before f9e6dfe341fb31c95b9655eb6b1db8b3ae090817affected · git
    • c521efd1700a8c0f7ce26f011f5eaecca17fabfa and later · before 594e1cf3f736779a535873fd5988162d827bfe4faffected · git
    • c521efd1700a8c0f7ce26f011f5eaecca17fabfa and later · before cf5a82bef623b969a609f2b7e392d06dbae34aa6affected · git
    • c521efd1700a8c0f7ce26f011f5eaecca17fabfa and later · before cb459fec4f7b13caf646101ff076e94ef38434d8affected · git
    • c521efd1700a8c0f7ce26f011f5eaecca17fabfa and later · before c1d87e724ae55e781b7cc7ccafb34d9e668582b2affected · git
    • before 2.6.33not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.187-16.1.187-1
Debian:12linux-6.12before 6.12.101-1~deb12u16.12.101-1~deb12u1
Debian:13linuxbefore 6.12.101-16.12.101-1
Debian:14linuxbefore 7.1.6-17.1.6-1

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-68173Aug 10, 2026 · ublk: wait on ublk_dev_ready() instead of ub->completion
    28Monitor
  • ← EarlierCVE-2026-68174Aug 10, 2026 · tracing: Fix union collision of module and refcnt for dynamic events
    0Monitor
  • Later →CVE-2026-68176Aug 10, 2026 · tracing: Fix mmiotrace possible NULL dereferencing of hiter->dev
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux1d0b59e2b203c02149d8f63607329debe36b3ec5Vendor (CNA)
Linux Linux581ac13e12e77d6c64f8719083bdf95209308919Vendor (CNA)
Linux Linux594e1cf3f736779a535873fd5988162d827bfe4fVendor (CNA)
Linux Linux7871128ea41217fa6a58bbbcb44cb0d2e9e60966Vendor (CNA)
Linux Linuxc1d87e724ae55e781b7cc7ccafb34d9e668582b2Vendor (CNA)
Linux Linuxcb459fec4f7b13caf646101ff076e94ef38434d8Vendor (CNA)
Linux Linuxcf5a82bef623b969a609f2b7e392d06dbae34aa6Vendor (CNA)
Linux Linuxf9e6dfe341fb31c95b9655eb6b1db8b3ae090817Vendor (CNA)
azl3 kernel 6.6.143.1-1 on Azure Linux 3.06.6.150.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.187-1 · Debian:12Package registry (OSV)
debian:linux-6.126.12.101-1~deb12u1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records