CVE-2026-43502: net/rds: handle zerocopy send cleanup before the message is queued
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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-43502?
CVE-2026-43502 has a risk rating of 27.
How do I fix CVE-2026-43502?
To fix CVE-2026-43502, ensure that you are using an updated version of the Linux kernel that addresses this vulnerability.
What systems are affected by CVE-2026-43502?
CVE-2026-43502 affects the net/rds component of the Linux kernel.
What type of vulnerability is CVE-2026-43502?
CVE-2026-43502 is a zerocopy send vulnerability within the Linux kernel.
When was CVE-2026-43502 published?
CVE-2026-43502 was published on May 21, 2026.