CVE-2026-43502
Last modified
CVE-2026-43502 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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. EPSS estimates a 0.12% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 4.17, < 5.10.258 | — |
| Linux | Linux Kernel | >= 5.11, < 5.15.209 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.175 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.140 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.88 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.30 | — |
| Linux | Linux Kernel | >= 6.19, < 7.0.7 | — |
| Linux | Linux Kernel | 7.1 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-43502?
How severe is CVE-2026-43502?
How do I fix CVE-2026-43502?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-43497In the Linux kernel, the following vulnerability has been re…7.3
- CVE-2026-43498In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-43499In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-4350The Perfmatters plugin for WordPress is vulnerable to arbitr…8.1
- CVE-2026-43500In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-43501In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-43503In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-43504An issue was discovered in Prosody before 0.12.6 and 1.0.0 t…6.5
- CVE-2026-43505An issue was discovered in Prosody before 0.12.6 and 1.0.0 t…6.5
- CVE-2026-43506An issue was discovered in Prosody before 0.12.6 and 1.0.0 t…7.5
- CVE-2026-43507An issue was discovered in Prosody before 0.12.6 and 1.0.0 t…7.5
- CVE-2026-4351The Perfmatters plugin for WordPress is vulnerable to arbitr…8.1
Are you affected by CVE-2026-43502?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
