linux: In the Linux kernel, the following vulnerability has been resolved: io_uring/nop: fix file reference leak with IOSQE...
CVE-2026-64426 is fixed in 20 products on 1 platform, first by ALAS2023-2026-2045, released August 3, 2026. It is not reported as exploited. Patch Radar priority: Routine.
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.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| bpftool6.18 · amzn 2023 | 1:6.18.39-79.141.amzn2023 | ALAS2023-2026-2045 | Aug 3, 2026 |
| bpftool6.18-debuginfo · amzn 2023 | 1:6.18.39-79.141.amzn2023 | ALAS2023-2026-2045 | Aug 3, 2026 |
| kernel-livepatch-6.18.39-79.141 · amzn 2023 | 1:1.0-0.amzn2023 | ALAS2023-2026-2045 | Aug 3, 2026 |
| kernel6.18 · amzn 2023 | 1:6.18.39-79.141.amzn2023 | ALAS2023-2026-2045 | Aug 3, 2026 |
| kernel6.18-debuginfo · amzn 2023 | 1:6.18.39-79.141.amzn2023 | ALAS2023-2026-2045 | Aug 3, 2026 |
| kernel6.18-debuginfo-common-aarch64 · amzn 2023 | 1:6.18.39-79.141.amzn2023 | ALAS2023-2026-2045 | Aug 3, 2026 |
| kernel6.18-debuginfo-common-x86_64 · amzn 2023 | 1:6.18.39-79.141.amzn2023 | ALAS2023-2026-2045 | Aug 3, 2026 |
| kernel6.18-devel · amzn 2023 | 1:6.18.39-79.141.amzn2023 | ALAS2023-2026-2045 | Aug 3, 2026 |
| kernel6.18-headers · amzn 2023 | 1:6.18.39-79.141.amzn2023 | ALAS2023-2026-2045 | Aug 3, 2026 |
| kernel6.18-modules-extra · amzn 2023 | 1:6.18.39-79.141.amzn2023 | ALAS2023-2026-2045 | Aug 3, 2026 |
| kernel6.18-modules-extra-common · amzn 2023 | 1:6.18.39-79.141.amzn2023 | ALAS2023-2026-2045 | Aug 3, 2026 |
| kernel6.18-tools · amzn 2023 | 1:6.18.39-79.141.amzn2023 | ALAS2023-2026-2045 | Aug 3, 2026 |
| kernel6.18-tools-debuginfo · amzn 2023 | 1:6.18.39-79.141.amzn2023 | ALAS2023-2026-2045 | Aug 3, 2026 |
| kernel6.18-tools-devel · amzn 2023 | 1:6.18.39-79.141.amzn2023 | ALAS2023-2026-2045 | Aug 3, 2026 |
| linux · Debian 14 | 7.1.4-1 | DEBIAN-CVE-2026-64426 | Aug 7, 2026 |
| microvm-kernel6.18 · amzn 2023 | 1:6.18.39-79.141.amzn2023 | ALAS2023-2026-2045 | Aug 3, 2026 |
| perf6.18 · amzn 2023 | 1:6.18.39-79.141.amzn2023 | ALAS2023-2026-2045 | Aug 3, 2026 |
| perf6.18-debuginfo · amzn 2023 | 1:6.18.39-79.141.amzn2023 | ALAS2023-2026-2045 | Aug 3, 2026 |
| python3-perf6.18 · amzn 2023 | 1:6.18.39-79.141.amzn2023 | ALAS2023-2026-2045 | Aug 3, 2026 |
| python3-perf6.18-debuginfo · amzn 2023 | 1:6.18.39-79.141.amzn2023 | ALAS2023-2026-2045 | Aug 3, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.