In the Linux kernel, the following vulnerability has been resolved: io_uring/nop: fix file reference leak with IOSQE_FIXED_FILE NOP file-acquisition… (CVE-2026-64426)
A vulnerability in the Linux kernel's io_uring NOP file-acquisition mechanism caused a file reference leak when IOSQE_FIXED_FILE was set without the corresponding IORING_NOP_FIXED_FILE flag. This led to a memory leak due to unreleased file references. The issue has been resolved by aligning the fixed file acquisition logic with the REQ_F_FIXED_FILE flag during request preparation.
AI Analysis
Technical Summary
The Linux kernel's io_uring subsystem had a flaw in its NOP file-acquisition path where a file reference leak occurred if a NOP request was submitted with the IOSQE_FIXED_FILE flag set but without the IORING_NOP_FIXED_FILE flag. The code path incorrectly handled file references, causing io_put_file() to not release a reference acquired via io_file_get_normal(), resulting in a memory leak. The fix involved using the REQ_F_FIXED_FILE flag consistently to decide between fixed and normal file acquisition, folding IORING_NOP_FIXED_FILE into REQ_F_FIXED_FILE at preparation time, thus preventing the leak.
Potential Impact
The vulnerability causes a memory leak in the Linux kernel due to unreleased file references in the io_uring NOP operation. This can lead to resource exhaustion over time, potentially affecting system stability or performance. There is no indication of direct code execution or privilege escalation from this issue.
Mitigation Recommendations
A fix for this vulnerability has been implemented in the Linux kernel. Users should apply the official kernel updates that include this patch to resolve the file reference leak. Since this is a kernel-level issue, upgrading to a patched kernel version is the recommended remediation. Patch status is not explicitly confirmed in the provided data; users should consult the Linux kernel vendor advisory or distribution security updates for the exact fixed versions and apply them accordingly.
In the Linux kernel, the following vulnerability has been resolved: io_uring/nop: fix file reference leak with IOSQE_FIXED_FILE NOP file-acquisition… (CVE-2026-64426)
Description
A vulnerability in the Linux kernel's io_uring NOP file-acquisition mechanism caused a file reference leak when IOSQE_FIXED_FILE was set without the corresponding IORING_NOP_FIXED_FILE flag. This led to a memory leak due to unreleased file references. The issue has been resolved by aligning the fixed file acquisition logic with the REQ_F_FIXED_FILE flag during request preparation.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel's io_uring subsystem had a flaw in its NOP file-acquisition path where a file reference leak occurred if a NOP request was submitted with the IOSQE_FIXED_FILE flag set but without the IORING_NOP_FIXED_FILE flag. The code path incorrectly handled file references, causing io_put_file() to not release a reference acquired via io_file_get_normal(), resulting in a memory leak. The fix involved using the REQ_F_FIXED_FILE flag consistently to decide between fixed and normal file acquisition, folding IORING_NOP_FIXED_FILE into REQ_F_FIXED_FILE at preparation time, thus preventing the leak.
Potential Impact
The vulnerability causes a memory leak in the Linux kernel due to unreleased file references in the io_uring NOP operation. This can lead to resource exhaustion over time, potentially affecting system stability or performance. There is no indication of direct code execution or privilege escalation from this issue.
Mitigation Recommendations
A fix for this vulnerability has been implemented in the Linux kernel. Users should apply the official kernel updates that include this patch to resolve the file reference leak. Since this is a kernel-level issue, upgrading to a patched kernel version is the recommended remediation. Patch status is not explicitly confirmed in the provided data; users should consult the Linux kernel vendor advisory or distribution security updates for the exact fixed versions and apply them accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-w7v4-jwp5-gr92
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64426"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a6542099c2644c7f80832e6
Added to database: 07/25/2026, 23:08:57 UTC
Last enriched: 07/25/2026, 23:22:28 UTC
Last updated: 07/25/2026, 23:22:28 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.