LiveActive security incident?Get immediate response
CVE Record

CVE-2025-68814: io_uring: fix filename leak in __io_openat_prep()

In the Linux kernel, the following vulnerability has been resolved: io_uring: fix filename leak in __io_openat_prep() __io_openat_prep() allocates a struct filename using getname(). However, for the condition of the file being installed in the fixed file table as well as having O_CLOEXEC flag set, the function returns early. At that point, the request doesn't have REQ_F_NEED_CLEANUP flag set. Due to this, the memory for the newly allocated struct filename is not cleaned up, causing a memory leak. Fix this by setting the REQ_F_NEED_CLEANUP for the request just after the successful getname() call, so that when the request is torn down, the filename will be cleaned up, along with other resources needing cleanup.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2025-68814 is a Linux kernel memory leak in io_uring open-file handling. A narrow error path can leave a filename allocation unreleased. The source bundle does not show data theft, privilege escalation, or active exploitation, but kernel memory leaks can matter for availability on affected systems.

Executive priority

Treat as a routine kernel maintenance item unless exposed systems are multi-tenant or availability-critical. Prioritize normal patch cycles and vendor advisory tracking over emergency response.

Technical view

In __io_openat_prep(), getname() allocates struct filename. When fixed-file table installation is requested together with O_CLOEXEC, the function returns early before REQ_F_NEED_CLEANUP is set, so teardown misses the filename allocation. Kernel stable fixes set cleanup tracking immediately after successful getname().

Likely exposure

Exposure is most likely on Linux systems running affected kernel versions or downstream builds before the listed stable fixes. Systems where io_uring is disabled or restricted may have reduced exposure. The bundle does not provide complete distribution package mappings.

Exploitation context

The bundle provides no KEV listing, exploit report, or public weaponization evidence. Any practical impact appears local and availability-oriented, but the sources do not prove a repeatable denial-of-service scenario.

Researcher notes

The core issue is cleanup-state ordering after getname(). The affected-version data in the bundle is incomplete and commit-oriented, so validation should rely on kernel source lineage, distro backports, and vendor advisories rather than raw upstream version labels alone.

Mitigation direction

  • Update to vendor kernel packages containing the referenced stable fixes.
  • Review Linux distribution advisories for exact fixed package versions.
  • For Siemens environments, review SSA-019113 for product-specific guidance.
  • Consider restricting io_uring where operationally feasible and vendor-supported.

Validation and detection

  • Inventory kernel versions across Linux hosts and appliances.
  • Map installed kernels to distribution advisories or the listed stable commits.
  • Check whether io_uring is enabled or restricted by local policy.
  • Confirm Siemens-managed products against SSA-019113 if applicable.
Prepared
Confidence
medium
Sources
9

Public sources used

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-68814 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
1ADP providers
8Source 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.

ADP provider summaries

siemens-SADPADP container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxb9445598d8c60a1379887b957024b71343965f74, b9445598d8c60a1379887b957024b71343965f74, b9445598d8c60a1379887b957024b71343965f74, b9445598d8c60a1379887b957024b71343965f74, b9445598d8c60a1379887b957024b71343965f74, b9445598d8c60a1379887b957024b71343965f74unaffected
LinuxLinux5.15, 0, 5.15.198, 6.1.160, 6.6.120, 6.12.64, 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.