What is CVE-2026-64467?

CVE-2026-64467 is a High severity Linux kernel vulnerability with a CVSS score of 8.8 out of 10, affecting Linux kernel versions from 6.18 onward and patched in 6.18.39, 7.1.4 and 7.2. CVE-2026-64467 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is the CVSS score for CVE-2026-64467?

CVE-2026-64467 has a CVSS score of 8.8 out of 10, rated High severity. The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H.

Is there a patch available for CVE-2026-64467?

Yes, CVE-2026-64467 has been patched. Fixed versions include 6.18.39, 7.1.4 and 7.2. If you are running Linux kernel 6.18 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2026-64467 actively exploited?

CVE-2026-64467 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

CVE-2026-64467

High

In the Linux kernel, the following vulnerability has been resolved: rust_binder: use a u64 stride when cleaning up the offsets array Allocation's Drop walks the offsets array (binder_size_t = u64 entries), cleaning up the objects, but it used usize instead of u64 for both the stride and the per-entry read. On 64-bit kernels (usize == u64) this is harmless, but on 32-bit kernels it walks the 8-byte entries in 4-byte steps, iterating an N-entry array 2N times, and reads the always-zero high word as offset 0, cleaning up the object at offset 0 N extra times. As a result the referenced node or handle ends up with a lower reference count than it actually has (a refcount over-decrement), and binder's reference accounting is corrupted; for example, the owner can be notified of a strong reference release (BR_RELEASE) even though references still remain. Change the stride to u64, and read each entry as a u64, narrowing it to usize with try_into(). On 32-bit ARM, when this over-decrement would drive a count below zero, the driver's existing refcount guard refuses it and fires: rust_binder: Failure: refcount underflow!

Package Linux Kernel

Published 2026-07-25

Last modified 2026-08-17

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

8.8

out of 10

High

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Vector string

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Affected versions

Linux kernel versions 6.18 and later are affected. Fixed in 6.18.39, 7.1.4, 7.2 and their respective stable series.

Affected from

≥ 6.18

Fixed in

✓ 6.18.39 6.18.x ✓ 7.1.4 7.1.x ✓ 7.2

References

3 total

Details

CVE ID CVE-2026-64467

Severity High

CVSS score 8.8 / 10

CVSS version 3.1

Published 2026-07-25

Modified 2026-08-17

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2026-64467?

CVE-2026-64467 is a High severity Linux kernel vulnerability with a CVSS score of 8.8 out of 10 . It affects Linux kernel versions from 6.18 onward and has been patched in 6.18.39, 7.1.4 and 7.2. CVE-2026-64467 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2026-64467?

CVE-2026-64467 has a CVSS score of 8.8 out of 10, rated High severity (CVSS 3.1). The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H.
Is there a patch available for CVE-2026-64467?

Yes. CVE-2026-64467 has been patched. Fixed versions include 6.18.39, 7.1.4 and 7.2. If you are running Linux kernel 6.18 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2026-64467 actively exploited?

No. CVE-2026-64467 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.