In the Linux kernel, the following vulnerability has been resolved: rust_binder: use a u64 stride when cleaning up the offsets array Allocation's… (CVE-2026-64467)
A vulnerability in the Linux kernel's rust_binder component caused incorrect reference counting on 32-bit kernels due to using usize instead of u64 when processing an offsets array. This led to over-decrementing reference counts, corrupting binder's reference accounting and potentially triggering refcount underflow errors. The issue is harmless on 64-bit kernels but affects 32-bit architectures like ARM. The vulnerability has been resolved by correcting the stride and read size to u64 with proper conversion.
AI Analysis
Technical Summary
The Linux kernel rust_binder vulnerability (CVE-2026-64467) involves improper handling of the offsets array during Allocation's Drop cleanup. The code used usize instead of u64 for stride and per-entry reads, causing 32-bit kernels to iterate the array incorrectly and over-decrement reference counts. This reference count corruption can lead to erroneous notifications of reference releases and refcount underflow errors, particularly on 32-bit ARM where the driver guards against underflow and triggers a failure. The fix changes the stride to u64 and reads each entry as u64, converting safely to usize.
Potential Impact
On 32-bit Linux kernels, this vulnerability corrupts binder's reference counting by over-decrementing reference counts, which can cause incorrect release notifications and refcount underflow errors. This undermines the integrity of binder's reference management, potentially affecting kernel stability or causing unexpected behavior in binder-related operations. On 64-bit kernels, the issue is harmless. There are no known exploits in the wild.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to correct the stride and read size to u64 with safe conversion, resolving the reference count corruption issue. Users should apply the official kernel update containing this fix. Since this is a kernel-level vulnerability, upgrading to the patched kernel version is the recommended remediation. Patch status is not explicitly confirmed in the provided data; check the vendor advisory or Linux kernel mailing lists for the exact fixed version and update accordingly.
In the Linux kernel, the following vulnerability has been resolved: rust_binder: use a u64 stride when cleaning up the offsets array Allocation's… (CVE-2026-64467)
Description
A vulnerability in the Linux kernel's rust_binder component caused incorrect reference counting on 32-bit kernels due to using usize instead of u64 when processing an offsets array. This led to over-decrementing reference counts, corrupting binder's reference accounting and potentially triggering refcount underflow errors. The issue is harmless on 64-bit kernels but affects 32-bit architectures like ARM. The vulnerability has been resolved by correcting the stride and read size to u64 with proper conversion.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel rust_binder vulnerability (CVE-2026-64467) involves improper handling of the offsets array during Allocation's Drop cleanup. The code used usize instead of u64 for stride and per-entry reads, causing 32-bit kernels to iterate the array incorrectly and over-decrement reference counts. This reference count corruption can lead to erroneous notifications of reference releases and refcount underflow errors, particularly on 32-bit ARM where the driver guards against underflow and triggers a failure. The fix changes the stride to u64 and reads each entry as u64, converting safely to usize.
Potential Impact
On 32-bit Linux kernels, this vulnerability corrupts binder's reference counting by over-decrementing reference counts, which can cause incorrect release notifications and refcount underflow errors. This undermines the integrity of binder's reference management, potentially affecting kernel stability or causing unexpected behavior in binder-related operations. On 64-bit kernels, the issue is harmless. There are no known exploits in the wild.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to correct the stride and read size to u64 with safe conversion, resolving the reference count corruption issue. Users should apply the official kernel update containing this fix. Since this is a kernel-level vulnerability, upgrading to the patched kernel version is the recommended remediation. Patch status is not explicitly confirmed in the provided data; check the vendor advisory or Linux kernel mailing lists for the exact fixed version and update accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-jcch-xvf6-72qc
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64467"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a6542089c2644c7f8082cc3
Added to database: 07/25/2026, 23:08:56 UTC
Last enriched: 07/25/2026, 23:19:44 UTC
Last updated: 07/26/2026, 05:10:31 UTC
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.