Menu

Star on GitHub · 3.2k

CVE-2026-64109

8.8 · HIGH

In the Linux kernel, the following vulnerability has been resolved: af_unix: Fix UAF read of tail->len in unix_stream_data_wait() unix_stream_data_wait() does skb_peek_tail(&sk->sk_receive_queue)…

Published Jul 19, 2026CWE-416EPSS 0.13%

Overview

CVE-2026-64109 is a high-severity vulnerability. It was published on July 19, 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. Some level of privileges is required for exploitation.

Technical description

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

af_unix: Fix UAF read of tail->len in unix_stream_data_wait()

unix_stream_data_wait() does skb_peek_tail(&sk->sk_receive_queue) without

holding any lock that prevents SKBs on that queue from being dequeued and

freed.

This has been the case since commit 79f632c71bea ("unix/stream: fix

peeking with an offset larger than data in queue").

The first consequence of this is that the pointer comparison

`tail != last` can be false even if `last` semantically refers to an

already-freed SKB while `tail` is a new SKB allocated at the same address;

which can cause unix_stream_data_wait() to wrongly keep blocking after new

data has arrived, but only in a weird scenario where a peeking recv() and

a normal recv() on the same socket are racing, which is probably not a

real problem.

But since commit 2b514574f7e8 ("net: af_unix: implement splice for stream

af_unix sockets"), `tail` is actually dereferenced, which can cause UAF in

the

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.

Frequently asked questions

What is CVE-2026-64109?

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

How severe is CVE-2026-64109?

This vulnerability has a CVSS 3.1 base score of 8.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

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

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-64109?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-64109 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