net/rds: handle zerocopy send cleanup before the message is queued
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.258, 5.15.209, 6.1.175, 6.6.140, 6.12.88, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 0cebaccef3acbdfbc2d85880a2efb765d2f4e2e3 · fixed in e9aefdc5c53fe9aed108c14e3d155710a1bb14c9; From 0cebaccef3acbdfbc2d85880a2efb765d2f4e2e3 · fixed in 46662f7dc59475995609bf3e9d27eb36f4acf26f; From 0cebaccef3acbdfbc2d85880a2efb765d2f4e2e3 · fixed in 1e262db7675e27f42c3f3f47d6011855f4454f24; From 0cebaccef3acbdfbc2d85880a2efb765d2f4e2e3 · fixed in 21d70744e6d3bbf9293aa1ee6fba7c53ad75275e; From 0cebaccef3acbdfbc2d85880a2efb765d2f4e2e3 · fixed in 3abc8983b2bae3f487f77d9da5527d7d6b210d46; From 0cebaccef3acbdfbc2d85880a2efb765d2f4e2e3 · fixed in 14ef6fd18db2494098b21e0471bf27a1d8e9993e; From 0cebaccef3acbdfbc2d85880a2efb765d2f4e2e3 · fixed in 0f5c185fc79a59ee9991234dd6d2a3e5afa6e75b; From 0cebaccef3acbdfbc2d85880a2efb765d2f4e2e3 · fixed in 44b550d88b267320459d518c0743a241ab2108fa
- Linux Linux
4.17
- KernelLinux
From 4.17.0 · fixed in 5.10.258; From 5.11.0 · fixed in 5.15.209; From 5.16.0 · fixed in 6.1.175; From 6.2.0 · fixed in 6.6.140; From 6.7.0 · fixed in 6.12.88; From 6.13.0 · fixed in 6.18.30; From 6.19.0 · fixed in 7.0.7
References 8
git.kernel.org
- stable/c/e9aefdc5c53fe9aed108c14e3d155710a1bb14c9
- stable/c/46662f7dc59475995609bf3e9d27eb36f4acf26f
- stable/c/1e262db7675e27f42c3f3f47d6011855f4454f24
- stable/c/21d70744e6d3bbf9293aa1ee6fba7c53ad75275e
- stable/c/3abc8983b2bae3f487f77d9da5527d7d6b210d46
- stable/c/14ef6fd18db2494098b21e0471bf27a1d8e9993e
- stable/c/0f5c185fc79a59ee9991234dd6d2a3e5afa6e75b
- stable/c/44b550d88b267320459d518c0743a241ab2108fa