CVE-2026-43433: rust_binder: avoid reading the written value in offsets array
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
Event History
Frequently Asked Questions
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.
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.
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.
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.
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.