CVE-2026-43433: rust_binder: avoid reading the written value in offsets array

Published May 8, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

rustbinder: avoid reading the written value in offsets array

When sending a transaction, its offsets array is first copied into the target proc's vma, and then the values are read back from there. This is normally fine because the vma is a read-only mapping, so the target process cannot change the value under us.

However, if the target process somehow gains the ability to write to its own vma, it could change the offset before it's read back, causing the kernel to misinterpret what the sender meant. If the sender happens to send a payload with a specific shape, this could in the worst case lead to the receiver being able to privilege escalate into the sender.

The intent is that gaining the ability to change the read-only vma of your own process should not be exploitable, so remove this TOCTOU read even though it's unexploitable without another Binder bug.

Affected Software

6 affected components
Linux Linux kernel
Linux Linux kernel>=6.18<6.18.19
Linux Linux kernel>=6.19<6.19.9
Linux Linux kernel=7.0-rc1
Linux Linux kernel=7.0-rc2
Linux Linux kernel=7.0-rc3

Event History

May 8, 2026
CVE Published
via MITRE·02:22 PM
Data Sourced
via MITRE·02:22 PM
DescriptionSeverity
Data Sourced
via NVD·03:16 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-43433?

CVE-2026-43433 has a medium severity level due to its potential impact on data integrity in transactions.

2

How do I fix CVE-2026-43433?

To fix CVE-2026-43433, update your Linux kernel to the latest patched version provided by your distribution.

3

What are the potential impacts of CVE-2026-43433?

The potential impacts of CVE-2026-43433 include data corruption and improper handling of memory transactions.

4

Which versions of Linux kernel are affected by CVE-2026-43433?

CVE-2026-43433 affects various versions of the Linux kernel prior to the official fix release.

5

Is CVE-2026-43433 being actively exploited?

As of now, there are no confirmed reports of active exploitation of CVE-2026-43433 in the wild.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203