https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 04:51:31 +0000 https://vulnerability.circl.lu/vuln/cve-2024-26926 <p><strong>Affected:</strong> Linux, linux_kernel</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>binder: check offset alignment in binder_get_object()</p> <p>Commit 6d98eb95b450 (&#34;binder: avoid potential data leakage when copying txn&#34;) 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() -&gt; check_buffer().</p> <p>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.</p> <p>It is worth noting this check existed prior to commit 7a67a39320df (&#34;binder: add function to copy binder object from buffer&#34;), likely removed due to redundancy at the time.</p> <p><strong>Affected:</strong> Linux, linux_kernel</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>binder: check offset alignment in binder_get_object()</p> <p>Commit 6d98eb95b450 (&#34;binder: avoid potential data leakage when copying txn&#34;) 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() -&gt; check_buffer().</p> <p>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.</p> <p>It is worth noting this check existed prior to commit 7a67a39320df (&#34;binder: add function to copy binder object from buffer&#34;), likely removed due to redundancy at the time.</p> https://vulnerability.circl.lu/vuln/cve-2024-26926