binder: fix leaked fd fixups on TF_UPDATE_TXN supersede
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 9864bb4801331daa48514face9d0f4861e4d485b · < c4c02084d6687d5cd5edccaf52cc45e5160f1184| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
binder: fix leaked fd fixups on TF_UPDATE_TXN supersede
When a TF_UPDATE_TXN transaction supersedes a pending async transaction in a frozen process, the outdated transaction is freed with kfree() directly. This skips binder_free_txn_fixups(), leaking all binder_txn_fd_fixup entries and their fget()'d struct file references.
The leaked file refcounts never reach zero, so the struct file objects are permanently pinned in memory. They survive process exit and accumulate across invocations until file-max exhaustion.
Every other transaction cleanup path (binder_free_transaction(), binder_transaction() error paths, binder_release_work()) correctly calls binder_free_txn_fixups(). Add the missing call before kfree() in the t_outdated cleanup block.
From the CVE record · Linux
The Linux kernel’s binder component leaks file references when a TF_UPDATE_TXN transaction supersedes a pending asynchronous transaction in a frozen process. Repeated occurrences can permanently pin file objects, eventually exhausting file-max. The input does not specify attacker access or authentication requirements.
Engineers running the Linux kernel should check affected versions against the vendor advisory; no version range is provided.