Linux kernel async reader loss in FIFO writer setup
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 76398425bb06b07cc3a3b1ce169c67dc9d6874ed · < 4c42ce499ce4b1c787e61082e3b13df4f30c4eaa| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
pipe: preserve existing fasync readers on writer setup failure
F_SETFL and FIOASYNC decide whether to invoke ->fasync() before pipe_fasync() takes pipe->mutex. Two enables of one O_RDWR FIFO can therefore both enter the callback.
fasync_helper() allocates before checking for an existing entry. If the first enable installs both entries, a second enable can update the reader entry and then fail the allocation for the writer entry. The error path removes the pre-existing reader entry, clearing FASYNC while the writer entry remains registered. __fput() then skips ->fasync(), so a later pipe notification can dereference the freed file or its f_owner. An unprivileged memory-pressure reproducer triggers a KASAN slab-use-after-free in send_sigio() through this path.
Keep the reader helper's result and undo the registration only if this call added it. The pipe mutex serializes changes to both lists, so a failed new registration still removes its reader, while a failed duplicate preserves the existing registrations and FASYNC. Successful duplicate enables continue to update fa_fd as before.
From the CVE record · Linux
Concurrent FIOASYNC or F_SETFL enables on an O_RDWR FIFO can leave a writer registration in place after a reader registration is incorrectly removed. Under memory pressure, an unprivileged local process can trigger a use-after-free during a later pipe notification. No user interaction is described.
Engineers running Linux kernels should check whether their kernel includes the pipe fasync fix; affected versions were not specified.