Kernel memory leak via mismatched file-reference flags
Published Jul 25, 2026 · Updated Jul 25, 2026
A resource leak in the io_uring NOP handler in Linux Kernel allows local users to consume kernel memory through crafted requests. The io_nop() path obtains a normal file reference when IOSQE_FIXED_FILE is set without IORING_NOP_FIXED_FILE, but io_put_file() treats the request as fixed and never releases that reference. Exploitation requires local access to submit the conflicting NOP flags; repeated requests accumulate unreleased file objects, with no published privilege-escalation or data-access impact.
Summary
What happened
A resource leak in the io_uring NOP handler in Linux Kernel allows local users to consume kernel memory through crafted requests. The io_nop() path obtains a normal file reference when IOSQE_FIXED_FILE is set without IORING_NOP_FIXED_FILE, but io_put_file() treats the request as fixed and never releases that reference. Exploitation requires local access to submit the conflicting NOP flags; repeated requests accumulate unreleased file objects, with no published privilege-escalation or data-access impact.
The record
- CVE
- CVE-2026-64426
- Published
- Jul 25, 2026
- Updated
- Jul 25, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1499.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 25, 2026CVE publishedPublication date reported by the CVE source.
- Jul 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.13
- Affected versionversion=a85f31052bce52111b4e9d5a536003481d0421d0 <2564ca2e31bd8ee8348362941af2ee4671e487ca
- Affected versionversion=a85f31052bce52111b4e9d5a536003481d0421d0 <722869fcff598fad20d5ab79c305897a7534708b
- Affected versionversion=a85f31052bce52111b4e9d5a536003481d0421d0 <7267717f35787167fcce4bc14f6ef3fa06682dcf
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo