VulnerabilityPublished 18 Oct 2026

CVE-2026-98776: Linux kernel · binderfs: fix UAF write in binder_add_device

Source GCVE Database

Authoritative record:CVE-2026-98776· High

Not known to be exploited : upgrade to 885bbbe52d31856768de439e9720f1ffa474a93a or 30d15f44a9e513ec2f257fdf192d9d1fa5af0799 soon.

Data as of 26 Oct 2026, 13:47 UTC

Severity

High

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 885bbbe52d31856768de439e9720f1ffa474a93a, 30d15f44a9e513ec2f257fdf192d9d1fa5af0799

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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-72x3-g5cv-hfvj

What to do

Upgrade Linux kernel to 885bbbe52d31856768de439e9720f1ffa474a93a or 30d15f44a9e513ec2f257fdf192d9d1fa5af0799.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ b89aa544821d5018002829fce5d10c9d00cc567f, < 885bbbe52d31856768de439e9720f1ffa474a93a	Fixed in 885bbbe52d31856768de439e9720f1ffa474a93a
LinuxLinux	Affected ≥ b89aa544821d5018002829fce5d10c9d00cc567f, < 30d15f44a9e513ec2f257fdf192d9d1fa5af0799	Fixed in 30d15f44a9e513ec2f257fdf192d9d1fa5af0799
LinuxLinux	Affected =6.19	Fixed in–
Debiandebian/linux`pkg:deb/debian/linux`Other threats	Affected =6.19	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix for this vulnerability has been implemented in the Linux kernel. Users and administrators should apply the official kernel updates that include this patch to remediate the issue. Patch status is not explicitly stated in the input data, so verify with the vendor advisory for the exact fixed kernel versions.

Description

A use-after-free (UAF) vulnerability in the Linux kernel's binderfs subsystem was resolved. The issue occurs when binderfs_binder_device_create() publishes a new device entry and releases locks and references, allowing a concurrent unlink operation to free the device. Subsequent access in binder_add_device() leads to a write to freed memory, causing a UAF condition.

Impact

This vulnerability allows a use-after-free write in kernel memory, which can lead to kernel memory corruption. While the exact exploitation impact is not detailed, such conditions can potentially cause system crashes or privilege escalation if exploited.

Summary

The vulnerability in the Linux kernel's binderfs arises from a race condition between publishing a new device dentry and registering it in the global binder_devices list. After simple_done_creating() releases the parent directory lock and drops the creator's dentry reference, a concurrent unlinkat() can remove the device entry, triggering binderfs_evict_inode() to free the device. Later, binder_add_device() accesses this freed object, resulting in a use-after-free write. This was detected by KASAN during testing with a modified Syzkaller tool.

References

Community reviews

Loading reviews…