Files
Kyle Zeng 8d5ce4751f net/rds: Do not unpin a page after a failed atomic pin
rds_cmsg_atomic() assumes that a non-NULL output from rds_pin_pages()
represents a pin that it owns. However, pin_user_pages_fast() can roll
back a fast-GUP pin after racing fork() and then fail in the slow path,
for example after a concurrent mprotect(PROT_NONE). The output slot can
still contain the already-unpinned page.

The common error path calls unpin_user_page() on that stale pointer.
This can consume another subsystem's pin and allow the page to be freed
while it is still in use. A local unprivileged reproducer triggers a
KASAN use-after-free write through an io_uring registered buffer.

Clear page when rds_pin_pages() does not return one. The error path
continues to release the page on errors after a successful pin, and
successful requests retain their existing ownership and behavior. All
four RDS atomic ancillary operations share this path.

The issue was found by an LLM.

Fixes: 15133f6e67 ("RDS: Implement atomic operations")
Cc: [email protected]
Signed-off-by: Kyle Zeng <[email protected]>
Reviewed-by: Allison Henderson <[email protected]>
Signed-off-by: Dave Miller <[email protected]>
2026-11-11 10:22:20 +00:00
..
…
2026-09-25 18:09:46 -07:00
2026-06-11 12:19:05 +02:00
…
2026-10-05 16:04:49 -07:00
2026-01-13 12:27:03 +01:00