From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 2395616EBF3 for ; Wed, 24 Apr 2024 23:10:38 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1714000239; cv=none; b=O/c1rr01PMJlrgQzNuvBU3w4vEYTx+asH2sYSRJkhvq9Qs5KsYKXEvZBUScGmNT6J5QA6A3ebJNKyRf0qU39L7LiVTup8TJWimi4wQoEQbN5I241hepLRLdJaU+6sueMAv0j57SA5wNmwvyxMw4x2PxOM6rhEoGYvC9csyYoIkw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1714000239; c=relaxed/simple; bh=NQE9RJUfcwZ7EAmyd4JTFBFw2qmYgmbq0COkfDwq+xI=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=A3+JEwJK2e6Dmf6cOnV8J8SwyueKyD89HUaNxTymdlWHEw0Q72SV8VYYCQIlWa/hzRKQ7rVUbhOJVD8PYHmuNHIiGC1C0a+pVnHAZdv/S7bYW+FCprLeK7f07fCgg8aLO/eQ/pyXS5IRYY6HNBIc5pW+Uxz6nW2oHVNryeANnWM= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=KI6BiDtD; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="KI6BiDtD" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 8B534C113CD; Wed, 24 Apr 2024 23:10:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1714000238; bh=NQE9RJUfcwZ7EAmyd4JTFBFw2qmYgmbq0COkfDwq+xI=; h=From:To:Cc:Subject:Date:Reply-to:From; b=KI6BiDtDYhAJFt5y5m1w6NxFteslZjvTNJSNtQAvSbN+7dOOlxsXz62X0ky/fKMnS y3vbyOtqbY59eW+uwPuf6cNszSh5ko3D5kOeIYWEtoZoUiEG1ex2bf0FVy2mc++u/z YmaYeBYHZyUc5Gjwqa1yfKkLTX6lap52+CrjIa2t320PzvAek70bGO8oAboltkRRbS 6yvXuoRmhzIcbgaRzILOfpG2aI4ep/Ty2v5ugsAQqmTjOvHdzt6zliCiASUfkel0RR 5ghJpljiD/gzsV9SlBkI0w/qla17cWGve5+O7SNKFAveBNwhaDjZGgpjpsBw8RQv9a ozBIMrQrvlABA== From: Lee Jones To: linux-cve-announce@vger.kernel.org Cc: Lee Jones Subject: CVE-2024-26922: binder: check offset alignment in binder_get_object() Date: Wed, 24 Apr 2024 16:10:32 -0700 Message-ID: <20240424231031.709209-2-lee@kernel.org> X-Mailer: git-send-email 2.44.0.769.g3c40516874-goog Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Reply-to: , X-Developer-Signature: v=1; a=openpgp-sha256; l=2357; i=lee@kernel.org; h=from:subject; bh=NQE9RJUfcwZ7EAmyd4JTFBFw2qmYgmbq0COkfDwq+xI=; b=owEBbQKS/ZANAwAKAVGvii+H/HdhAcsmYgBmKZFoW+xZQRQwmIysRNdRGReJKaGO/m2oNIcfx bGekXNMENCJAjMEAAEKAB0WIQR2tsk1o74gmpTwh0hRr4ovh/x3YQUCZimRaAAKCRBRr4ovh/x3 YZKUD/4rpWcJ2fE88rTYKTlgI62ecLNq7yht9HmnZ41q9WxUMrOJXqQbFRo2TZwv9e4niCoST1+ 95idcSzOhzkcy9fESWbvolbPJ0VxUZ3Zg4VTMR5Swyc8a1MMJHi2KihRz1wPKsrrdqDgYeJIzd8 6DZ7ze2IGRYH2KnfQt//j4sVmnmTaEIs/oG8vptwrW++f8izhOKZbcsKBTBzGiGmuwkQjgZR198 PsTS/ek52tmy8KGtaeVvIVZiUg0iR0QlEVvENWKoJbGCfEuivQxfjtGmww/w0ydQOAcfhlcymMn I0/pLwfsKeFtaQxEOcsOsWmmH69RzRws68UDiqywLGd3DHyHeAm0nXk1kjMEMtymrgYDIkASIMX Z/a2cZvWfcp2VWvXx/Ek0+3qi+HeK4ZcxAoHZSl8gdv2kSs/vYZgLzIcFF33C9FiTuY5frJn9+9 TH+oMcQ7KfBaoCRrVHsvqvia4Nf18nByR1/ePR7EqYVPbFc1bifegx2ufyfMqsqYHHd8bWIxqHv vi2CeQ6bHKwxm1vV/Z6qZUz69PzqwQJDwWWVLtOSzoPkvWzz/V0SZJHNQpqsEVyn+VHhcD7s6xb FidxirwkM+PI3o/z/Up63o2UYhSFfwYqCfOwuIFCcZq63LZ3JmQkOzke6GNAcjbKhf6BBtWHcHM ia4u3izyKMWkiGA== X-Developer-Key: i=lee@kernel.org; a=openpgp; fpr=76B6C935A3BE209A94F0874851AF8A2F87FC7761 Content-Transfer-Encoding: 8bit Description =========== 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. The Linux kernel CVE team has assigned CVE-2024-26922 to this issue. Affected and fixed versions =========================== Issue introduced in 5.17 with commit 6d98eb95b450 and fixed in 6.9-rc5 with commit aaef73821a3b Issue introduced in 5.4.226 with commit c056a6ba35e0 Issue introduced in 5.10.157 with commit 23e9d815fad8 Issue introduced in 5.15.17 with commit 7a9ad4aceb02 Issue introduced in 5.16.3 with commit 66e12f5b3a97 Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2024-26922 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: drivers/android/binder.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: https://git.kernel.org/stable/c/aaef73821a3b0194a01bd23ca77774f704a04d40