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

Published Jan 13, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

iouring: fix filename leak in ioopenatprep()

ioopenatprep() allocates a struct filename using getname(). However, for the condition of the file being installed in the fixed file table as well as having OCLOEXEC flag set, the function returns early. At that point, the request doesn't have REQFNEEDCLEANUP 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 REQFNEEDCLEANUP 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.

Affected Software

3 affected componentsFixes available
Linux Linux kernel
Microsoft azl3 kernel 6.6.119.3-3
debian/linux
6.1.176-16.1.190-16.12.107-16.12.115-27.2.12-17.2.15-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.113-1Fixed in 7.2.12-1Fixed in 7.2.13-1
  2. Compensating control

    In __io_openat_prep(), set the REQ_F_NEED_CLEANUP flag on the request immediately after a successful getname() call so the allocated struct filename is released during request teardown, including the fixed-file-table and O_CLOEXEC early-return path.

Event History

Jan 13, 2026
CVE Published
via MITRE·03:29 PM
Data Sourced
via MITRE·03:29 PM
Description
Data Sourced
via NVD·04:16 PM
Description
Jan 15, 2026
Data Sourced
via Microsoft·09:03 AM
DescriptionSeverityWeaknessAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of CVE-2025-68814?

CVE-2025-68814 has a moderate severity rating due to its impact on information leakage.

2

How do I fix CVE-2025-68814?

To fix CVE-2025-68814, update your Linux kernel to the latest stable version provided by your distribution.

3

What causes the CVE-2025-68814 vulnerability?

CVE-2025-68814 is caused by a filename leak in the __io_openat_prep() function within the Linux kernel.

4

Which versions of the Linux kernel are affected by CVE-2025-68814?

CVE-2025-68814 affects multiple versions of the Linux kernel prior to the release of the patch.

5

Is CVE-2025-68814 exploitable in production environments?

Yes, CVE-2025-68814 could be exploited in production environments if systems are running affected versions of the Linux kernel.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203