Skip to content
Fencer Intel
high 7.8

CVE-2024-26926 json

binder: check offset alignment in binder_get_object()

published 2y ago modified 3mo ago also EUVD-2024-24188

cvss
7.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 39%
public exploits
0
none known

Summary

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.

Patch / fix

  • Linux Linux 5.4.275, 5.10.216, 5.15.157, 5.17, 6.1.88, 6.6.29, 6.8.8, 6.9
  • linux linux_kernel 1d7f1049035b, 48a1f83ca9c6, 68a28f551e46, a2fd6dbc98be, a6d2a8b211c8, aaef73821a3b, f01d66190457
  • linux Debian 12 6.1.90-1
  • linux Debian 14, Debian 13 6.8.9-1

debian advisories DEBIAN-CVE-2024-26926

  • linux Ubuntu 20.04 LTS 5.4.0-189.209
  • linux Ubuntu 22.04 LTS 5.15.0-116.126
  • linux Ubuntu 24.04 LTS 6.8.0-38.38
  • linux-aws Ubuntu 20.04 LTS 5.4.0-1128.138
  • linux-aws Ubuntu 22.04 LTS 5.15.0-1065.71
  • linux-aws Ubuntu 24.04 LTS 6.8.0-1011.12
  • linux-gcp Ubuntu 20.04 LTS 5.4.0-1132.141
  • linux-gcp Ubuntu 22.04 LTS 5.15.0-1064.72

ubuntu advisories UBUNTU-CVE-2024-26926

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2024-26926 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-26926 updated cvss 4.4

kernel: binder: check offset alignment in binder_get_object()

  • Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more
    affected: no fix planned “Out of support scope”
  • Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more
    affected: no fix available, no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

cisa ICSA-25-226-15 updated cvss 0.0

Siemens SINEC OS

  • Siemens RUGGEDCOM RST2428P (6GK6242-6PA00) < 3.1 Siemens SCALANCE XCM-/XRM-/XCH-/XRH-300 family < 3.1
    affected: fixed in V3.1 support.industry.siemens.com
  • Siemens SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family
    not affected

Facts from CISA's republication of the vendor's own advisory (CSAF); the linked advisory is the authoritative source. CISA notification · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
2y ago

Exploit prediction

0.44% chance of exploitation in the next 30 days, higher than 39% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected products

  • Linux Linux
  • linux linux_kernel

Classification

Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.