Linux Kernel up to 6.12.112/6.18.55/7.2.9/7.3-rc5 Binder binder_release_entire_buffer is_failure multiple operations on resource in single-operation context

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.2$0-$5k0.46-

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Linux Kernel up to 6.12.112/6.18.55/7.2.9/7.3-rc5. This affects the function binder_release_entire_buffer of the component Binder. This manipulation of the argument is_failure causes multiple operations on resource in single-operation context. This vulnerability is tracked as CVE-2026-98778. The attack is restricted to local execution. No exploit exists. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.12.112/6.18.55/7.2.9/7.3-rc5. It has been declared as problematic. Affected by this vulnerability is the function binder_release_entire_buffer of the component Binder. The manipulation of the argument is_failure with an unknown input leads to a multiple operations on resource in single-operation context vulnerability. The CWE definition for the vulnerability is CWE-675. The product performs the same operation on a resource two or more times, when the operation should only be applied once. As an impact it is known to affect integrity, and availability. The summary by CVE is:

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.

The advisory is shared at git.kernel.org. This vulnerability is known as CVE-2026-98778 since 09/25/2026. The exploitation appears to be easy. An attack has to be approached locally. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/18/2026).

Upgrading to version 6.12.113, 6.18.56, 7.2.10 or 7.3-rc6 eliminates this vulnerability. Applying the patch 60a9f7323ae7318a7cce0d387c318da24f1e8726/86cdcc87d4ba60aebf94ba3346b3c900c5cd79ff/1ab671b50714ad8e359cf37eb041d8044319ccdc/22c135635fdd9816c0ef140d6de7b2e4fdf73e89 is able to eliminate this problem. The best possible mitigation is suggested to be upgrading to the latest version.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.4
VulDB Meta Temp Score: 4.2

VulDB Base Score: 4.4
VulDB Temp Score: 4.2
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Multiple operations on resource in single-operation context
CWE: CWE-675
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: No

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.12.113/6.18.56/7.2.10/7.3-rc6
Patch: 60a9f7323ae7318a7cce0d387c318da24f1e8726/86cdcc87d4ba60aebf94ba3346b3c900c5cd79ff/1ab671b50714ad8e359cf37eb041d8044319ccdc/22c135635fdd9816c0ef140d6de7b2e4fdf73e89

Timelineinfo

09/25/2026 CVE reserved
10/18/2026 +23 days Advisory disclosed
10/18/2026 +0 days VulDB entry created
10/18/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-98778 (🔒)
GCVE (CVE): GCVE-0-2026-98778
GCVE (VulDB): GCVE-100-422017

Entryinfo

Created: 10/18/2026 19:51
Changes: 10/18/2026 19:51 (60)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Want to know what is going to be exploited?

We predict KEV entries!