Bug 1223388 (CVE-2024-26926) - VUL-0: CVE-2024-26926: kernel: binder: check offset alignment in binder_get_object()
Summary: VUL-0: CVE-2024-26926: kernel: binder: check offset alignment in binder_get_o...
Status: RESOLVED INVALID
Alias: CVE-2024-26926
Product: SUSE Security Incidents
Classification: Novell Products
Component: Incidents (show other bugs)
Version: unspecified
Hardware: Other Other
: P3 - Medium : Normal
Target Milestone: ---
Assignee: Security Team bot
QA Contact: Security Team bot
URL: https://smash.suse.de/issue/403114/
Whiteboard: CVSSv3.1:SUSE:CVE-2024-26926:6.1:(AV:...
Keywords:
Depends on:
Blocks:
 
Reported: 2024-04-25 10:59 UTC by SMASH SMASH
Modified: 2024-04-25 16:17 UTC (History)
2 users (show)

See Also:
Found By: Security Response Team
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description SMASH SMASH 2024-04-25 10:59:54 UTC
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.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-26926
https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-26926.mbox
https://git.kernel.org/stable/c/aaef73821a3b0194a01bd23ca77774f704a04d40
https://www.cve.org/CVERecord?id=CVE-2024-26926
Comment 1 Ivan Ivanov 2024-04-25 15:58:19 UTC
We do not build binder, thus not affected. Back to security team.
Comment 2 Camila Camargo de Matos 2024-04-25 16:17:52 UTC
Thanks for the update! If we are not affected, I will be closing this issue now.