# CVE-2024-26926: binder: check offset alignment in binder_get_object()

> Missing offset alignment check in the Linux kernel binder driver allows memory corruption, potentially leading to privilege escalation or code execution.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Apr 2024
- **Updated:** 5 Aug 2026
- **Also known as:** A-320661088, ASB-A-320661088, BELL-CVE-2024-26926, DEBIAN-CVE-2024-26926, GHSA-g993-hcw2-pmmf, UBUNTU-CVE-2024-26926

## What is CVE-2024-26926?

CVE-2024-26926 is a high-severity memory corruption vulnerability in Debian Debian Linux, published on 24 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2024-26926?

It affects 2 products.


Products: Debian Debian Linux, Linux kernel.

## How do I fix CVE-2024-26926?

Apply the vendor's patch.

## Is CVE-2024-26926 being exploited?

There is no known exploitation of CVE-2024-26926 in the wild and no public exploit code.

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-26926 and fix it if it is affected.

What it is: CVE-2024-26926 is a high-severity memory corruption vulnerability in Debian Debian Linux, published on 24 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-26926 in the wild and no public exploit code.

Affected product: Debian Debian Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-26926/ (Markdown: https://insights.sbomify.com/CVE-2024-26926/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-26926
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-26926
- OSV: https://osv.dev/vulnerability/CVE-2024-26926

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-26926/
Summaries are generated and may contain mistakes; the official description above is the record.