CVE-2026-43435: Linux kernel · rust_binder: fix oneway spam detection
Source GCVE Database
Not known to be exploited.
Data as of 27 Oct 2026, 00:07 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Exploitation evidence
Disclosed: evidence found.
CVE published 8 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
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.
References
- nvd.nist.gov/vuln/detail/CVE-2026-43435 (opens in a new tab)
- git.kernel.org/stable/c/4fc87c240b8f30e22b7ebaae29d57105589e1c0b (opens in a new tab)
- git.kernel.org/stable/c/8d34c993a9a156e657e43cb95186980745cc3597 (opens in a new tab)
- git.kernel.org/stable/c/edf685946c4acbe57cb96f8d5f3c07e9a2e973c8 (opens in a new tab)