binder: fix is_failure flag for superseded transaction cleanup
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 9864bb4801331daa48514face9d0f4861e4d485b · < 22c135635fdd9816c0ef140d6de7b2e4fdf73e89| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
binder: fix is_failure flag for superseded transaction cleanup
When a TF_UPDATE_TXN transaction supersedes a pending async transaction, binder_release_entire_buffer() is called with is_failure=false. Since the superseded transaction was never delivered, binder_apply_fd_fixups() was never called and no fds were installed in the target process.
With is_failure=false, the BINDER_TYPE_FDA cleanup handler interprets stale buffer contents as installed fd numbers and passes them to binder_deferred_fd_close(), closing unrelated file descriptors.
Pass is_failure=true since the transaction was never delivered to the target, matching the semantics of all other undelivered-transaction cleanup paths.
From the CVE record · Linux
The Linux kernel's binder cleanup can treat stale buffer contents as installed file descriptors when a TF_UPDATE_TXN transaction supersedes a pending asynchronous transaction that was never delivered. This can close unrelated file descriptors in the target process. The input does not specify attacker access requirements or user interaction.
Engineers running the Linux kernel should check whether their kernel includes the binder fix; affected versions are not specified.