Description
In 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.
Product status
eafedbc7c050c44744fbdf80bdf3315e860b7513 (git) before e19afb53f7723b3bd22224f2b0c7dcfa70bb973f
eafedbc7c050c44744fbdf80bdf3315e860b7513 (git) before 3672141c93b7a0c0132bf5d5021a4b7f1d663aaa
eafedbc7c050c44744fbdf80bdf3315e860b7513 (git) before 4cb9e13fec0de7c942f5f927469beb8e48ddd20f
6.18
Any version before 6.18
6.18.19 (semver)
6.19.9 (semver)
7.0 (original_commit_for_fix)
References
git.kernel.org/...c/e19afb53f7723b3bd22224f2b0c7dcfa70bb973f
git.kernel.org/...c/3672141c93b7a0c0132bf5d5021a4b7f1d663aaa
git.kernel.org/...c/4cb9e13fec0de7c942f5f927469beb8e48ddd20f