rust_binder: avoid reading the written value in offsets array
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.18.196.19.97.0In the Linux kernel, the following vulnerability has been resolved:
rust_binder: 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.
From the CVE record · Linux
The Linux kernel's rust_binder component reads transaction offsets back from the receiving process's mapping after copying them there. If the receiver can write to that normally read-only mapping and the sender sends a payload with a specific shape, the receiver could potentially escalate privileges into the sender. Exploitation requires another Binder bug that enables the write.
Engineers running Linux kernels with rust_binder should check their exposure; affected versions were not specified.