CVE-2021-46935binder: fix async_free_space accounting for empty parcels
- 5.5MediumCVSS base score
- 0.23%Exploitation in 30 daysEPSS · top 86% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: binder: fix async_free_space accounting for empty parcels In 4.13, commit 74310e06be4d ("android: binder: Move buffer out of area shared with user space") fixed a kernel structure visibility issue. As part of that patch, sizeof(void *) was used as the buffer size for 0-length data payloads so the driver could detect abusive clients sending 0-length asynchronous transactions to a server by enforcing limits on async_free_size. Unfortunately, on the "free" side, the accounting of async_free_space did not add the sizeof(void *) back. The result was that up to 8-bytes of async_free_space were leaked on every async transaction of 8-bytes or less. These small transactions are uncommon, so this accounting issue has gone undetected for several years. The fix is to use "buffer_size" (the allocated buffer size) instead of "size" (the logical buffer size) when updating the async_free_space during the free operation. These are the same except for this corner case of asynchronous transactions with payloads < 8 bytes.
Timeline
ID reserved
By Linux
- 2 days later
· 2 days later
Published
- 2 years later
· 2 years later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
- EPSS (exploitation in 30 days)
- 0.23% · top 86% of all CVEs (18 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 74310e06be4d74dcf67cd108366710dee5c576d5 – < 2d2df539d05205fd83c404d5f2dff48d36f9b495
- affected 74310e06be4d74dcf67cd108366710dee5c576d5 – < 7c7064402609aeb6fb11be1b4ec10673ff17b593
- affected 74310e06be4d74dcf67cd108366710dee5c576d5 – < 103b16a8c51f96d5fe063022869ea906c256e5da
- affected 74310e06be4d74dcf67cd108366710dee5c576d5 – < 1cb8444f3114f0bb2f6e3bcadcf09aa4a28425d4
- affected 74310e06be4d74dcf67cd108366710dee5c576d5 – < 17691bada6b2f1d5f1c0f6d28cd9d0727023b0ff
- affected 74310e06be4d74dcf67cd108366710dee5c576d5 – < cfd0d84ba28c18b531648c9d4a35ecca89ad9901
- affected 4.14
- unaffected < 4.14
- unaffected 4.14.261 – ≤ 4.14.*
- unaffected 4.19.224 – ≤ 4.19.*
- unaffected 5.4.170 – ≤ 5.4.*
- unaffected 5.10.90 – ≤ 5.10.*
- unaffected 5.15.13 – ≤ 5.15.*
- unaffected 5.16 – ≤ *
References
References6
- https://git.kernel.org/stable/c/2d2df539d05205fd83c404d5f2dff48d36f9b495 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/7c7064402609aeb6fb11be1b4ec10673ff17b593 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/103b16a8c51f96d5fe063022869ea906c256e5da (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/1cb8444f3114f0bb2f6e3bcadcf09aa4a28425d4 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/17691bada6b2f1d5f1c0f6d28cd9d0727023b0ff (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/cfd0d84ba28c18b531648c9d4a35ecca89ad9901 (opens in a new tab)x_transferred
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2021-33583 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2021-46935)Record last updated .