binder: check offset alignment in binder_get_object()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 6d98eb95b450a75adb4516a1d33652dc78d2b20c · < f01d6619045704d78613b14e2e0420bfdb7f1c15| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel's binder_get_object() lost an offset alignment check when object copying changed to use copy_from_user(). The missing check can complicate later object unwinding; the input does not specify an attacker outcome or the access and interaction needed to trigger it.
Teams running the Linux kernel should check whether their version is affected; affected versions are not specified.