rust_binder: fix oneway spam detection
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: 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.
From the CVE record · Linux
The Linux kernel's rust_binder component has gaps in one-way transaction spam detection: TreeRange omits the current request from its calculation, and ArrayRange lacks equivalent detection. An attacker sending one-way transactions could evade this detection; the input does not specify whether this requires local or network access, authentication, or user interaction.
Teams running Linux kernels with rust_binder should check their exposure; affected versions are not specified.