LiveActive security incident?Get immediate response
CVE Record

CVE-2025-68791: fuse: missing copy_finish in fuse-over-io-uring argument copies

In the Linux kernel, the following vulnerability has been resolved: fuse: missing copy_finish in fuse-over-io-uring argument copies Fix a possible reference count leak of payload pages during fuse argument copies. [Joanne: simplified error cleanup]

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2025-68791 is a Linux kernel FUSE issue where some fuse-over-io_uring argument-copy error handling can leak references to payload pages. In practical terms, it may waste kernel memory/resources over time. Public sources do not provide a CVSS score or evidence of active exploitation.

Executive priority

Treat as a stability and resource-exhaustion risk. Patch during the next kernel maintenance window, faster for shared Linux platforms or systems relying heavily on FUSE.

Technical view

The kernel fix adds missing cleanup for FUSE argument copies using fuse-over-io_uring. The CVE describes a possible reference count leak of payload pages. The affected data points to Linux kernel versions around 6.14 through fixes in 6.18.3/6.19, but distribution backports require vendor confirmation.

Likely exposure

Exposure is most relevant on Linux systems running affected kernels where FUSE and fuse-over-io_uring paths are available or used. Remote exposure is not established by the provided sources.

Exploitation context

No KEV listing or cited source indicates active exploitation. The described impact is a resource/reference leak, so the most plausible concern is local resource exhaustion or stability impact, not confirmed code execution.

Researcher notes

The public record is sparse: no CVSS, CWE, exploit report, or detailed attack prerequisites are provided. Analysis should focus on the referenced kernel commits and distribution backports rather than assuming upstream version numbers map directly to deployed risk.

Mitigation direction

  • Update to a kernel containing the referenced stable fixes.
  • Check your Linux distribution advisory for backported fixed packages.
  • Prioritize shared, multi-user, container, and FUSE-heavy hosts.
  • If patching is delayed, consult vendor guidance on limiting affected functionality.

Validation and detection

  • Inventory Linux kernel versions across affected assets.
  • Confirm whether vendor kernels include the referenced stable commits.
  • Review package changelogs for CVE-2025-68791 or the FUSE fix title.
  • Identify hosts using FUSE workloads or fuse-over-io_uring.
  • Monitor patched hosts for abnormal kernel memory/resource behavior.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-68791 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
3Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxc090c8abae4b6b77a1bee116aa6c385456ebef96, c090c8abae4b6b77a1bee116aa6c385456ebef96unaffected
LinuxLinux6.14, 0, 6.18.3, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.