fuse: fix race between interrupt and resend
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
fuse: fix race between interrupt and resend
After commit f8fce75fedf7 ("fuse: clear intr_entry in fuse_resend and fuse_remove_pending_req") the WARN_ON(!list_empty(&req->intr_entry)) in fuse_request_free() still triggers due to the following race:
In request_wait_answer() if (test_bit(FR_SENT, &req->flags)) -> returns true
In fuse_chan_resend() clear_bit(FR_SENT, &req->flags)
In request_wait_answer() queue_interrupt(req)
Fix by:
- move clearing FR_SENT inside fpq->lock
From the CVE record · Linux
A race between interrupt handling and request resending in the Linux kernel’s FUSE code can trigger a warning when a request is freed. It occurs when an interrupt is queued while a request is being resent; the input does not establish an attacker-controlled path, authentication requirement, or user-interaction requirement.
Engineers running Linux kernels with the affected FUSE request-handling code should check their versions; no affected version range is provided.