VulnerabilityPublished 18 Oct 2026

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

Affects Linux kernelSource CVE Database V5

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

Data as of 26 Oct 2026, 10:12 UTC

Severity

High

Rated High by Threat Radar's AI analysis · 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.

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 is available in the Linux kernel commits 885bbbe52d31856768de439e9720f1ffa474a93a and 30d15f44a9e513ec2f257fdf192d9d1fa5af0799. Users and administrators should update to a Linux kernel version that includes these fixes to remediate the issue.

Description

A use-after-free (UAF) vulnerability exists in the Linux kernel's binderfs subsystem, specifically in the binder_add_device function. The issue arises when a new device entry is published and then concurrently unlinked, causing the device object to be freed while still being accessed, leading to a write-after-free condition. This flaw was discovered through kernel address sanitizer (KASAN) testing and has been fixed in specific Linux kernel commits.

Impact

This vulnerability can lead to memory corruption due to use-after-free writes in the kernel, potentially causing system instability or enabling privilege escalation if exploited. However, no known exploits in the wild have been reported to date.

Summary

The vulnerability in the Linux kernel's binderfs involves a use-after-free write in the binder_add_device function. The binderfs_binder_device_create() function publishes a new dentry and releases the parent directory lock, after which a concurrent unlinkat() can remove the device entry. This triggers binderfs_evict_inode(), freeing the device object. Subsequently, binder_add_device() attempts to write to the freed object, causing a use-after-free condition. The issue was identified by a modified Syzkaller tool with KASAN reporting slab-use-after-free errors. The problem is fixed in Linux kernel commits 885bbbe52d31856768de439e9720f1ffa474a93a and 30d15f44a9e513ec2f257fdf192d9d1fa5af0799.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Oct 2026, 09:57 UTC

Technical details

References

Community reviews

Related threats