Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2026-64434

8.8 · HIGH

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix UAF in channel timeout by holding conn ref l2cap_chan_timeout() runs asynchronously and accesses chan->conn.

Published Jul 25, 2026EPSS 0.26%

Overview

CVE-2026-64434 is a high-severity vulnerability. It was published on July 25, 2026 and has a CVSS 3.1 base score of 8.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 8.8, rated HIGH. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: L2CAP: Fix UAF in channel timeout by holding conn ref

l2cap_chan_timeout() runs asynchronously and accesses chan->conn. If

the connection is torn down while the timer is running or pending,

chan->conn can be freed, leading to a use-after-free when the timer

worker attempts to lock conn->lock:

| BUG: KASAN: slab-use-after-free in instrument_atomic_read_write include/linux/instrumented.h:112 [inline]

| BUG: KASAN: slab-use-after-free in atomic_long_try_cmpxchg_acquire include/linux/atomic/atomic-instrumented.h:4456 [inline]

| BUG: KASAN: slab-use-after-free in __mutex_trylock_fast kernel/locking/mutex.c:161 [inline]

| BUG: KASAN: slab-use-after-free in mutex_lock+0x4f/0xa0 kernel/locking/mutex.c:318

| Write of size 8 at addr ffff8881298d9550 by task kworker/2:1/83

|

| CPU: 2 UID: 0 PID: 83 Comm: kworker/2:1 Not tainted 7.1.0-rc6-next-20260601-dirty #6 PREEMPT(full)

| Hardware name: QEMU Standard PC (i440FX

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refgit.kernel.org/stable/c/0b0e2bf39cf99e458d991b9df253727e036a7d7dRefgit.kernel.org/stable/c/32d783cafb46ff3ca58e6f9fd62c9c5f35eaf26bRefgit.kernel.org/stable/c/50c38d9f42a529691e4e67ea9cedf4f0bfc8d277Refgit.kernel.org/stable/c/8922c7940bae9ce4b1736dddb6362370793835c2Refgit.kernel.org/stable/c/8f90405a4a6f1f1880dc07996b47bf57c712bd8aRefgit.kernel.org/stable/c/91047a4396a8b1857a6f712a90cf33ec0012b189Refgit.kernel.org/stable/c/b66774b48dd98f07254951f74ea6f513efe7ff8bRefgit.kernel.org/stable/c/d3b739db5dc6f688a60d56da872fabaf65246032

How CyberStrike helps

Frequently asked questions

What is CVE-2026-64434?

CVE-2026-64434 is a high-severity vulnerability. It was published on July 25, 2026 and has a CVSS 3.1 base score of 8.8 (HIGH).

How severe is CVE-2026-64434?

This vulnerability has a CVSS 3.1 base score of 8.8, rated HIGH. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2026-64434?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-64434?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-64434 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2026

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999