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

Published Apr 24, 2024
·
Updated

In binderalloccopytobuffer of binder.c, there is a possible arbitrary code execution due to a use after free. This could lead to local escalation of privilege in the kernel with no additional execution privileges needed. User interaction is not needed for exploitation.

Other sources

In the Linux kernel, the following vulnerability has been resolved:

binder: check offset alignment in bindergetobject()

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 binderalloccopyfrombuffer() -> checkbuffer().

These calls were replaced in bindergetobject() with copyfromuser(), 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.

— NVD

Affected Software

17 affected componentsFixes available
Linux Linux kernel>=5.4.226<5.4.275
Linux Linux kernel>=5.10.157<5.10.216
Linux Linux kernel>=5.15.17<5.15.157
Linux Linux kernel>=5.16.3<6.1.88
Linux Linux kernel>=6.2<6.6.29
Linux Linux kernel>=6.7<6.8.8
Linux Linux kernel=6.9-rc1
Linux Linux kernel=6.9-rc2
Linux Linux kernel=6.9-rc3
Linux Linux kernel=6.9-rc4
Debian Debian Linux=10.0
Google Android
android/:linux_kernel:>=:0<:2024-06-05
:2024-06-05
debian/linux<6.1.90-1
6.1.90-1
debian/linux<6.8.9-1
6.8.9-1
debian/linux<6.8.9-1
6.8.9-1
debian/linux
6.1.176-16.1.190-16.12.107-16.12.115-27.2.12-17.2.15-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.1.90-1
  2. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.8.9-1
  3. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.115-2Fixed in 7.2.12-1Fixed in 7.2.15-1
  4. Upgrade

    Upgrade android/:linux_kernel: to a version that resolves this vulnerability.

    Fixed in :2024-06-05

Event History

Apr 24, 2024
CVE Published
via MITRE·11:23 PM
Data Sourced
via MITRE·11:23 PM
DescriptionSeverity
Apr 25, 2024
Data Sourced
via NVD·06:15 AM
RemedyDescriptionSeverityAffected Software
Data Sourced
via OSV·06:15 AM
DescriptionSeverityAffected Software
Jun 1, 2024
Advisory Published
via OSV·12:00 AM
Jun 3, 2024
Data Sourced
via Android·12:00 AM
SeverityWeaknessAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of CVE-2024-26926?

CVE-2024-26926 has a moderate severity rating due to the potential for data leakage in the Linux kernel's binder system.

2

How do I fix CVE-2024-26926?

To fix CVE-2024-26926, update to the patched versions of the Linux kernel or upgrade to the specified newer versions in the Debian package list.

3

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

CVE-2024-26926 affects specific versions of the Linux kernel, including 5.10.223-1, 5.10.226-1, 6.1.119-1, and 6.12.10-1.

4

Is CVE-2024-26926 relevant to Android users?

Yes, CVE-2024-26926 is relevant to Android users as it impacts the Linux kernel components used in the Android operating system.

5

What functions are impacted by CVE-2024-26926?

CVE-2024-26926 specifically impacts the binder_get_object() function in the Linux kernel, leading to potential data leakage.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203