High · published May 21, 2026
In the Linux kernel, the following vulnerability has been resolved:
net/rds: handle zerocopy send cleanup before the message is queued
A zerocopy send can fail after user pages have been pinned but before
the message is attached to the sending socket.
The purge path currently infers zerocopy state from rm->m_rs, so an
unqueued message can be cleaned up as if it owned normal payload pages.
However, zerocopy ownership is really determined by the presence of
op_mmp_znotifier, regardless of whether the message has reached the
socket queue.
Capture op_mmp_znotifier up front in rds_message_purge() and use it as
the cleanup discriminator. If the message is already associated with a
socket, keep the existing completion path. Otherwise, drop the pinned
page accounting directly and release the notifier before putting the
payload pages.
This keeps early send failure cleanup consistent with the zerocopy
lifetime rules without changing the normal queued completion path.
| Product | Versions | Fixed in |
|---|---|---|
| linux/linux_kernel | ≥ 4.17, < 5.10.258 | 5.10.258 |
| linux/linux_kernel | ≥ 5.11, < 5.15.209 | 5.15.209 |
| linux/linux_kernel | ≥ 5.16, < 6.1.175 | 6.1.175 |
| linux/linux_kernel | ≥ 6.2, < 6.6.140 | 6.6.140 |
| linux/linux_kernel | ≥ 6.7, < 6.12.88 | 6.12.88 |
| linux/linux_kernel | ≥ 6.13, < 6.18.30 | 6.18.30 |
| linux/linux_kernel | ≥ 6.19, < 7.0.7 | 7.0.7 |
| linux/linux_kernel | all versions | — |
| linux/linux_kernel | all versions | — |