VDB

CVE-2025-40220

CVE-2025-40220 PUBLISHED

fuse: fix livelock in synchronous file put from fuseblk workers

Reported by linux · Published December 4, 2025

In the Linux kernel, the following vulnerability has been resolved: fuse: fix livelock in synchronous file put from fuseblk workers I observed a hang when running generic/323 against a fuseblk server. This test opens a file, initiates a lot of AIO writes to that file descriptor, and closes the file descriptor before the writes complete. Unsurprisingly, the AIO exerciser threads are mostly stuck waiting for responses from the fuseblk server: # cat /proc/372265/task/372313/stack [<0>] request_wait_answer+0x1fe/0x2a0 [fuse] [<0>] __fuse_simple_request+0xd3/0x2b0 [fuse] [<0>] fuse_do_getattr+0xfc/0x1f0 [fuse] [<0>] fuse_file_read_iter+0xbe/0x1c0 [fuse] [<0>] aio_read+0x130/0x1e0 [<0>] io_submit_one+0x542/0x860 [<0>] __x64_sys_io_submit+0x98/0x1a0 [<0>] do_syscall_64+0x37/0xf0 [<0>] entry_SYSCALL_64_after_hwframe+0x4b/0x53 But the /weird/ part is that the fuseblk server threads are waiting for responses from itself: # cat /proc/372210/task/372232/stack [<0>] request_wait_answer+0x1fe/0x2a0 [fuse] [<0>] __fuse_simple_request+0xd3/0x2b0 [fuse] [<0>] fuse_file_put+0x9a/0xd0 [fuse] [<0>] fuse_release+0x36/0x50 [fuse] [<0>] __fput+0xec/0x2b0 [<0>] task_work_run+0x55/0x90 [<0>] syscall_exit_to_user_mode+0xe9/0x100 [<0>] do_syscall_64+0x43/0xf0 [<0>] entry_SYSCALL_64_after_hwframe+0x4b/0x53 The fuseblk server is fuse2fs so there's nothing all that exciting in the server itself. So why is the fuse server calling fuse_file_put? The commit message for the fstest sheds some light on that: "By closing the file descriptor before calling io_destroy, you pretty much guarantee that the last put on the ioctx will be done in interrupt context (during I/O completion). Aha. AIO fgets a new struct file from the fd when it queues the ioctx. The completion of the FUSE_WRITE command from userspace causes the fuse server to call the AIO completion function. The completion puts the struct file, queuing a delayed fput to the fuse server task. When the fuse server task returns to userspace, it has to run the delayed fput, which in the case of a fuseblk server, it does synchronously. Sending the FUSE_RELEASE command sychronously from fuse server threads is a bad idea because a client program can initiate enough simultaneous AIOs such that all the fuse server threads end up in delayed_fput, and now there aren't any threads left to handle the queued fuse commands. Fix this by only using asynchronous fputs when closing files, and leave a comment explaining why.

EPSS 0.21% · 10.7th percentile

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
kernelAmazon Linux1:6.1.158-178.288.amzn2023
kernel-libbpf-staticAmazon Linux1:6.1.158-178.288.amzn2023
kernel6.12-modules-extraAmazon Linux1:6.12.55-74.119.amzn2023
LinuxLinux2.6.35, 2.6.34, 2.6.33

Risk scores

EPSS Score
0.21%
10.7th percentile

Affected products

VendorProductVersions
LinuxLinux5a18ec176c934ca1bc9dc61580a5e0e90a9b5733, 5a18ec176c934ca1bc9dc61580a5e0e90a9b5733, 5a18ec176c934ca1bc9dc61580a5e0e90a9b5733
LinuxLinux2.6.38, 0, 5.10.246
amazon:2023kernel0
amazon:2023kernel-libbpf-static0
amazon:2023kernel6.12-modules-extra0
LinuxLinux2.6.37.3, 5a18ec176c934ca1bc9dc61580a5e0e90a9b5733, 5a18ec176c934ca1bc9dc61580a5e0e90a9b5733
amazon:2023kernel-modules-extra-common0
amazon:2023perf6.120
amazon:2023kernel-tools0
amazon:2023kernel6.12-tools-devel0
amazon:2023python3-perf6.120
amazon:2023kernel-headers0
amazon:2023kernel6.12-devel0
amazon:2023python3-perf0
amazon:2023kernel6.12-libbpf-devel0
amazon:2023perf0
amazon:2023bpftool0
amazon:2023kernel6.12-libbpf-static0
amazon:2023kernel6.12-libbpf0
amazon:2023kernel-libbpf0

…and 12 more

Timeline

  • Dec 4, 2025 CVE Published
  • Dec 5, 2025 EPSS Score (30 in total, the first dated here)
  • Mar 29, 2026 Distribution Patch (168 in total, the first dated here)
  • Mar 29, 2026 Security Advisory (218 in total, the first dated here)
  • Jun 8, 2026 Coalition ESS Score
  • Jun 17, 2026 CVE Updated

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2025-40220
vulnetix vdb fixes CVE-2025-40220

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-40220/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›