LiveActive security incident?Get immediate response
CVE Record

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

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2024-26926 is a Linux kernel Binder bug where a safety check for aligned object offsets was lost during an earlier code change. The source bundle does not provide CVSS, CWE, or confirmed impact details. Treat this as a kernel maintenance risk for systems using Binder, not as confirmed active exploitation.

Executive priority

Schedule remediation through normal kernel patch management, with higher priority for systems that expose Binder or run custom kernels. The absence of CVSS and exploitation evidence lowers confidence in urgency, but kernel IPC bugs should not remain indefinitely unpatched.

Technical view

The Binder function binder_get_object() began using copy_from_user() after commit 6d98eb95b450, bypassing the prior binder_alloc_copy_from_buffer() to check_buffer() alignment validation path. Stable fixes add an explicit offset alignment check to preserve the expected Binder object parsing invariant.

Likely exposure

Exposure is likely limited to Linux kernels in the affected commit or stable-version ranges where the Binder subsystem is present and reachable. The bundle lists Linux as the affected product but does not provide CPEs or a complete platform inventory.

Exploitation context

The bundle marks KEV as false and provides no cited evidence of active exploitation or public exploit tooling. It also does not state attacker position, privileges, or concrete security impact, so remote exploitability or business impact should not be assumed.

Researcher notes

Evidence supports a regression-style flaw: an existing alignment check was unintentionally removed when object copying changed. The record is technically specific but lacks severity scoring, CWE mapping, attacker requirements, and confirmed impact. Validate exposure through kernel version and Binder configuration rather than product assumptions.

Mitigation direction

  • Apply Linux kernel updates from your distribution or kernel vendor that include the referenced Binder fixes.
  • Prioritize assets with Binder enabled, custom kernels, or kernels matching affected source versions.
  • For Debian LTS, review the listed Debian advisory and install its kernel security update.
  • If no package exists, check vendor backport status against the referenced stable commits.

Validation and detection

  • Inventory running kernel versions and compare them with vendor advisories for CVE-2024-26926.
  • Confirm whether Binder support is built, loaded, or exposed on each Linux asset.
  • Verify the installed kernel includes one of the referenced stable fix commits or vendor backport.
  • Review kernel changelogs for binder_get_object offset alignment handling.
Prepared
Confidence
medium
Sources
10

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-26926 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
9Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxc056a6ba35e00ae943e377eb09abd77a6915b31a, 23e9d815fad84c1bee3742a8de4bd39510435362, 7a9ad4aceb0226b391c9d3b8e4ac2e7d438b6bde, 6d98eb95b450a75adb4516a1d33652dc78d2b20c, 6d98eb95b450a75adb4516a1d33652dc78d2b20c, 6d98eb95b450a75adb4516a1d33652dc78d2b20c, 6d98eb95b450a75adb4516a1d33652dc78d2b20c, 66e12f5b3a9733f941893a00753b10498724607d, 5.4.226, 5.10.157, 5.15.17, 5.16.3unaffected
LinuxLinux5.17, 0, 5.4.275, 5.10.216, 5.15.157, 6.1.88, 6.6.29, 6.8.8, 6.9affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.