fuse-uring: Avoid queue->stopped races and set/read that value under lock
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.18.397.1.47.2In the Linux kernel, the following vulnerability has been resolved:
fuse-uring: Avoid queue->stopped races and set/read that value under lock
There are several readers of queue->stopped that check the value under lock, but fuse_uring_commit_fetch() did not and actually the value was not set under the lock in fuse_uring_abort_end_requests() either. Especially in fuse_uring_commit_fetch it is important to check under a lock, because due to races 'struct fuse_req' might be freed with fuse_request_end, but another thread/cpu might already do teardown work.
From the CVE record · Linux
A race involving queue->stopped in the Linux kernel's fuse-uring code can allow a FUSE request to be freed while another thread or CPU is tearing it down. The input does not specify how an attacker could trigger the race or whether network access, authentication, or user interaction is required.
Engineers running the Linux kernel should check their installations; affected versions are not specified.