io_uring/nop: fix file reference leak with IOSQE_FIXED_FILE
Summary
| CVE | CVE-2026-64426 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-07-25 10:17:26 UTC |
| Updated | 2026-07-25 10:17:26 UTC |
| 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. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected a85f31052bce52111b4e9d5a536003481d0421d0 722869fcff598fad20d5ab79c305897a7534708b git |
Not specified |
| CNA |
Linux |
Linux |
affected a85f31052bce52111b4e9d5a536003481d0421d0 7267717f35787167fcce4bc14f6ef3fa06682dcf git |
Not specified |
| CNA |
Linux |
Linux |
affected a85f31052bce52111b4e9d5a536003481d0421d0 2564ca2e31bd8ee8348362941af2ee4671e487ca git |
Not specified |
| CNA |
Linux |
Linux |
affected 6.13 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.13 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.39 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.1.4 7.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2-rc1 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/722869fcff598fad20d5ab79c305897a7534708b |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/7267717f35787167fcce4bc14f6ef3fa06682dcf |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/2564ca2e31bd8ee8348362941af2ee4671e487ca |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.