{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-64467","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","state":"PUBLISHED","assignerShortName":"Linux","dateReserved":"2026-07-19T15:36:31.790Z","datePublished":"2026-07-25T08:51:32.626Z","dateUpdated":"2026-08-17T04:56:12.747Z"},"containers":{"cna":{"providerMetadata":{"orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux","dateUpdated":"2026-08-17T04:56:12.747Z"},"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nrust_binder: use a u64 stride when cleaning up the offsets array\n\nAllocation's Drop walks the offsets array (binder_size_t = u64 entries),\ncleaning up the objects, but it used usize instead of u64 for both the\nstride and the per-entry read.\n\nOn 64-bit kernels (usize == u64) this is harmless, but on 32-bit kernels\nit walks the 8-byte entries in 4-byte steps, iterating an N-entry array\n2N times, and reads the always-zero high word as offset 0, cleaning up\nthe object at offset 0 N extra times. As a result the referenced node or\nhandle ends up with a lower reference count than it actually has (a\nrefcount over-decrement), and binder's reference accounting is corrupted;\nfor example, the owner can be notified of a strong reference release\n(BR_RELEASE) even though references still remain.\n\nChange the stride to u64, and read each entry as a u64, narrowing it to\nusize with try_into().\n\nOn 32-bit ARM, when this over-decrement would drive a count below zero,\nthe driver's existing refcount guard refuses it and fires:\n\n  rust_binder: Failure: refcount underflow!"}],"metrics":[{"cvssV3_1":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","baseScore":8.8,"baseSeverity":"HIGH"},"scenarios":[{"lang":"en","value":"AV:L - The vulnerable path is reached through a local BINDER_WRITE_READ ioctl carrying a crafted Binder transaction.\nAC:L - The attacker controls object zero and the offsets count and can force synchronous cleanup with a later invalid object; no race or uncontrollable condition is required.\nPR:L - An ordinary process permitted to access the Binder device and invoke and transfer objects to the target can trigger the bug; no capability or administrative privilege is required.\nUI:N - A malformed later object makes transaction construction fail and invokes cleanup during the attacker's ioctl, without recipient or human action.\nS:C - Prematurely releasing an object owned by a more privileged Binder service can create a user-space use-after-free across the Android application sandbox boundary.\nC:H - The attacker can retain a handle after BR_RELEASE frees the owning service's object, then target the stale pointer and potentially obtain code execution and arbitrary access to privileged-process memory.\nI:H - Exploitation of the resulting stale Binder object can provide attacker-controlled code execution and arbitrary modification within the privileged owning service.\nA:H - Stale-object dispatch can crash a critical Binder service, and the trigger can be repeated to cause persistent service or system disruption."}]}],"affected":[{"product":"Linux","vendor":"Linux","defaultStatus":"unaffected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/android/binder/allocation.rs"],"versions":[{"version":"eafedbc7c050c44744fbdf80bdf3315e860b7513","lessThan":"89b8cc948dce661af87527623b3a41cdd115e2f9","status":"affected","versionType":"git"},{"version":"eafedbc7c050c44744fbdf80bdf3315e860b7513","lessThan":"74920b1b4e474ba7a4de4323c0458deec49d210b","status":"affected","versionType":"git"},{"version":"eafedbc7c050c44744fbdf80bdf3315e860b7513","lessThan":"803c8a9502e9b97cd6ae937618ef4a8fd6274343","status":"affected","versionType":"git"}]},{"product":"Linux","vendor":"Linux","defaultStatus":"affected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/android/binder/allocation.rs"],"versions":[{"version":"6.18","status":"affected"},{"version":"0","lessThan":"6.18","status":"unaffected","versionType":"semver"},{"version":"6.18.39","lessThanOrEqual":"6.18.*","status":"unaffected","versionType":"semver"},{"version":"7.1.4","lessThanOrEqual":"7.1.*","status":"unaffected","versionType":"semver"},{"version":"7.2","lessThanOrEqual":"*","status":"unaffected","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.18","versionEndExcluding":"6.18.39"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.18","versionEndExcluding":"7.1.4"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.18","versionEndExcluding":"7.2"}]}]}],"references":[{"url":"https://git.kernel.org/stable/c/89b8cc948dce661af87527623b3a41cdd115e2f9"},{"url":"https://git.kernel.org/stable/c/74920b1b4e474ba7a4de4323c0458deec49d210b"},{"url":"https://git.kernel.org/stable/c/803c8a9502e9b97cd6ae937618ef4a8fd6274343"}],"title":"rust_binder: use a u64 stride when cleaning up the offsets array","x_generator":{"engine":"bippy-1.2.0"}}}}