Description
In the Linux kernel, the following vulnerability has been resolved: rust_binder: fix oneway spam detection The spam detection logic in TreeRange was executed before the current request was inserted into the tree. So the new request was not being factored in the spam calculation. Fix this by moving the logic after the new range has been inserted. Also, the detection logic for ArrayRange was missing altogether which meant large spamming transactions could get away without being detected. Fix this by implementing an equivalent low_oneway_space() in ArrayRange. Note that I looked into centralizing this logic in RangeAllocator but iterating through 'state' and 'size' got a bit too complicated (for me) and I abandoned this effort.
Product status
eafedbc7c050c44744fbdf80bdf3315e860b7513 (git) before edf685946c4acbe57cb96f8d5f3c07e9a2e973c8
eafedbc7c050c44744fbdf80bdf3315e860b7513 (git) before 8d34c993a9a156e657e43cb95186980745cc3597
eafedbc7c050c44744fbdf80bdf3315e860b7513 (git) before 4fc87c240b8f30e22b7ebaae29d57105589e1c0b
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/edf685946c4acbe57cb96f8d5f3c07e9a2e973c8
git.kernel.org/...c/8d34c993a9a156e657e43cb95186980745cc3597
git.kernel.org/...c/4fc87c240b8f30e22b7ebaae29d57105589e1c0b