UBUNTU-CVE-2026-99203: Use After Free

Published Oct 28, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved: pipe: preserve existing fasync readers on writer setup failure FSETFL and FIOASYNC decide whether to invoke ->fasync() before pipefasync() takes pipe->mutex. Two enables of one ORDWR FIFO can therefore both enter the callback. fasynchelper() 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 fowner. An unprivileged memory-pressure reproducer triggers a KASAN slab-use-after-free in sendsigio() 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 fafd as before.

Event History

Oct 28, 2026
CVE Published
via OSV·12:00 AM
Data Sourced
via OSV·12:00 AM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

What conditions are required to trigger this issue?

The affected path involves two asynchronous-I/O enable operations on a single O_RDWR FIFO, where both can enter the fasync callback before the pipe mutex is acquired. The failure scenario requires allocation failure while setting up the writer-side asynchronous notification entry after an existing reader entry has been updated.

2

Can an unprivileged local user trigger it?

Yes. The provided reproducer is described as unprivileged and uses memory pressure to cause the allocation failure needed for the vulnerable error path.

3

How might the issue appear during testing or diagnostics?

A KASAN-enabled system can report a slab use-after-free in send_sigio() after the stale writer-side registration causes a later pipe notification to dereference a freed file or f_owner.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203