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.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A local user or process with low privileges may be able to abuse malformed Binder object offsets in affected Linux kernels. The missing alignment check can undermine kernel handling of Binder transactions, with potentially serious confidentiality, integrity, and availability consequences. The supplied evidence does not describe remote exploitation.

Executive priority

Treat this as high priority where untrusted local code can access Binder because potential impact spans data, integrity, and availability. Use an expedited kernel-remediation cycle, while confirming exposure and vendor backports before declaring systems vulnerable or fixed.

Technical view

A change replaced binder_alloc_copy_from_buffer/check_buffer with copy_from_user in binder_get_object, unintentionally dropping offset-alignment validation. The correction restores an explicit check before later object handling and unwind logic. CVSS 3.1 is 7.8: local access, low complexity, low privileges, no user interaction, and high impact ratings.

Likely exposure

Exposure requires an affected Linux kernel build using Binder and permitting an untrusted local process to reach it. The bundle mixes release numbers and commit hashes, so simple version comparison may be unreliable. Verify the running kernel's provenance, vendor backports, Binder configuration, and applicable stable-branch fix.

Exploitation context

No active exploitation is supported by the supplied evidence: KEV is false, and no cited source claims attacks or public exploit availability. CVSS indicates exploitation requires local, low-privileged access. Absence from KEV does not prove exploitation cannot occur.

Researcher notes

The regression followed commit 6d98eb95b450, which replaced the earlier buffer-copy path and lost alignment validation. The bundle provides multiple stable-branch correction commits but no CWE, proof of concept, exploit telemetry, or clearly normalized affected range. Map fixes by kernel branch rather than assuming one commit applies universally.

Mitigation direction

  • Upgrade to a vendor-supported kernel containing the applicable linked stable fix.
  • Follow distribution or device-vendor guidance when kernel lineage or backport status is unclear.
  • Restrict untrusted local access to Binder-capable systems until remediation, where operationally feasible.

Validation and detection

  • Record running kernel versions, build provenance, and Binder configuration on potentially exposed systems.
  • Confirm the applicable stable fix through vendor advisories or source and backport inspection.
  • Reboot after updating, then verify the running kernel matches the remediated package.
  • Review telemetry for Binder-related crashes; the supplied sources provide no specific exploitation indicators.
Prepared
Confidence
medium
Sources
9

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
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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.

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

SSVC decision data

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

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2024-26926Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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.