CVE-2026-98777: Linux kernel · binder: fix leaked fd fixups on TF_UPDATE_TXN supersede
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in c4c02084d6687d5cd5edccaf52cc45e5160f1184 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 17:16 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in c4c02084d6687d5cd5edccaf52cc45e5160f1184, a7329ea53d04f0c6135d02905810cd6f42acdf45, 6673f4f21e2fddfed0abe1eb9045cc958e6db130 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 18 Oct 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.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
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.
References
- git.kernel.org/stable/c/a7329ea53d04f0c6135d02905810cd6f42acdf45 (opens in a new tab)
- git.kernel.org/stable/c/7fd609fb0e9dcbc4d7a1e4da1af5368c0555ff55 (opens in a new tab)
- git.kernel.org/stable/c/1299cb3fb061598496086fc87ff291057831148e (opens in a new tab)
- git.kernel.org/stable/c/6673f4f21e2fddfed0abe1eb9045cc958e6db130 (opens in a new tab)
- git.kernel.org/stable/c/c4c02084d6687d5cd5edccaf52cc45e5160f1184 (opens in a new tab)