Skip to main content
VulnerabilityPublished Updated

CVE-2026-64426: Linux kernel · io_uring/nop: fix file reference leak with IOSQE_FIXED_FILE

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in 7267717f35787167fcce4bc14f6ef3fa06682dcf : update Linux kernel when convenient.

Data as of 6 Nov 2026, 17:04 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in 7267717f35787167fcce4bc14f6ef3fa06682dcf, 722869fcff598fad20d5ab79c305897a7534708b, 2564ca2e31bd8ee8348362941af2ee4671e487ca

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade Linux kernel to 7267717f35787167fcce4bc14f6ef3fa06682dcf, 722869fcff598fad20d5ab79c305897a7534708b or 2564ca2e31bd8ee8348362941af2ee4671e487ca.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ a85f31052bce52111b4e9d5a536003481d0421d0, < 7267717f35787167fcce4bc14f6ef3fa06682dcf
Fixed in
  • 7267717f35787167fcce4bc14f6ef3fa06682dcf
LinuxLinuxAffected
  • ≥ a85f31052bce52111b4e9d5a536003481d0421d0, < 722869fcff598fad20d5ab79c305897a7534708b
Fixed in
  • 722869fcff598fad20d5ab79c305897a7534708b
LinuxLinuxAffected
  • ≥ a85f31052bce52111b4e9d5a536003481d0421d0, < 2564ca2e31bd8ee8348362941af2ee4671e487ca
Fixed in
  • 2564ca2e31bd8ee8348362941af2ee4671e487ca
LinuxLinuxAffected
  • =6.13
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: io_uring/nop: fix file reference leak with IOSQE_FIXED_FILE NOP file-acquisition support choses between a fixed (registered) file and a normal fget()'d file based on its own IORING_NOP_FIXED_FILE flag in sqe->nop_flags. However, a request's REQ_F_FIXED_FILE is set independently from the generic IOSQE_FIXED_FILE sqe flag during request init, before the issue handler runs. If a NOP is submitted with IOSQE_FIXED_FILE set (so REQ_F_FIXED_FILE is set) but without IORING_NOP_FIXED_FILE, io_nop() takes the normal path and grabs a real reference via io_file_get_normal(). On completion, io_put_file() only drops the reference when REQ_F_FIXED_FILE is clear, so the fget()'d file is never released and leaks: BUG: memory leak unreferenced object 0xffff88800f42c240 (size 176): kmem_cache_alloc_noprof+0x358/0x440 alloc_empty_file+0x57/0x180 path_openat+0x44/0x1e50 do_file_open+0x121/0x200 do_sys_openat2+0xa7/0x150 __x64_sys_openat+0x82/0xf0 Decide between fixed and normal file acquisition from REQ_F_FIXED_FILE, the same way io_assign_file() does for every other opcode, and fold IORING_NOP_FIXED_FILE into REQ_F_FIXED_FILE at prep time.

References

Community reviews

Loading reviews…