From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (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 5DF2443D4EA for ; Wed, 26 Aug 2026 14:40:44 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1787755245; cv=none; b=hVTr2pqhYGBSht4K5qWR/7XtSbyQPDavXXfUpCQ1cvwlUpQnH9udA9/xZJKHfOC4NegT9qyMxUlacplr0Gx5uahEEQffy66g+eFZ4ozVtISOIDKTyVgSRsjX9jqF0PmHwtwBbWYB68UbnbJu7NVNNy7E11MC5Z+3OUYu8I6dRmc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1787755245; c=relaxed/simple; bh=Xr00KvUiC2VXBk81+W19o72fMhMcy6lzH9T7qs/EVto=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=Mdww0B5O8sl4CfqydM0Ja+/rzrtTK+4MqTmZ93ofvCyGK+5wzB6G8QdxC++G6RHnYgRD9qLSUtIQ93bxVByqe/fjL7uY1CHIOMniYVDlY5kXX7zuuuOXML0CCAPZvkqykoizDGd9WObXSNnZWRlEbDjAjP8tpHnTkbhd79dyP88= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=JNOXL9MQ; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="JNOXL9MQ" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 804AB1F000E9; Wed, 26 Aug 2026 14:40:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1787755244; bh=pZCePPbkoi+tZalN3Sfw18pr0Va3R+EVPgIrXvmvDn0=; h=From:To:Cc:Subject:Date:Reply-To; b=JNOXL9MQaSYOvAKHMJFMwAfJJ/8PhJMBconr635nsxlkxIVFjVQ6x1APPUSq5BJjT rpFhvmHzudGMGd9NOqFB3sfrYJbjlaQ8R8sS0437JdN07KD1V9U1UcBARaXRiPNJEC weM6ABFQ/oVPInsR0qjqO55x4y8BN9p2stpmFPUY= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-80575: Input: cs40l50-vibra - validate custom data from user space Date: Wed, 26 Aug 2026 16:38:11 +0200 Message-ID: <2026082613-CVE-2026-80575-644f@gregkh> X-Mailer: git-send-email 2.55.0 Reply-To: , Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=4024; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=vliXQ99dEa5L4lFHMvX0PsK/jKOU+OcPO3N27TWFE5o=; b=owGbwMvMwCRo6H6F97bub03G02pJDFl9v6SerdHY7nPy8Z3ttopTjrA5WayxMuzRubDlh0ny+ 9ZXl1bf7ohlYRBkYpAVU2T5so3n6P6KQ4pehranYeawMoEMYeDiFICJrNvAsGBlw4+5adMiHC6/ Dzqedl39o03vka8MC2Zb72DctC6H/57KSmUhlS+KT/O1pAE= X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman Description =========== In the Linux kernel, the following vulnerability has been resolved: Input: cs40l50-vibra - validate custom data from user space cs40l50_add() copies the custom data of an FF_PERIODIC/FF_CUSTOM effect straight from the ff_effect the user passed to EVIOCSFF, without requiring it to hold anything: work_data.custom_data = memdup_array_user(periodic->custom_data, periodic->custom_len, sizeof(s16)); work_data.custom_len = periodic->custom_len; The driver then reads two words out of that buffer: custom_data[0] as the waveform bank in cs40l50_effect_bank_set(), and custom_data[1] as the index within the bank in cs40l50_effect_index_set(). Neither read is covered by a length check, and custom_len is fully user controlled: - custom_len == 0 makes memdup_array_user() call memdup_user() with a length of zero, which returns ZERO_SIZE_PTR rather than an error, so custom_data[0] dereferences it. - custom_len == 1 allocates two bytes. A bank of ROM or RAM keeps effect->type out of the OWT case, and custom_data[1] is then read one word past the allocation. The bank value itself is also mishandled. It is masked with CS40L50_CUSTOM_DATA_MASK (0xffff) but stored in an s16, so a custom_data[0] of 0x8000 or above wraps to a negative value that passes the "bank_type >= CS40L50_WVFRM_BANK_NUM" test. cs40l50_effect_index_set() indexes vib->dsp.banks[] with it before the switch statement's default case gets a chance to reject it: base_index = vib->dsp.banks[effect->type].base_index; max_index = vib->dsp.banks[effect->type].max_index; Require the two words the driver reads to be present, and hold the masked bank in a u32 so the existing upper-bound test covers the whole range. The da7280 haptic driver already range checks custom_len this way. The Linux kernel CVE team has assigned CVE-2026-80575 to this issue. Affected and fixed versions =========================== Issue introduced in 6.11 with commit c38fe1bb5d21c2ce0857965ee06174ee587d6b42 and fixed in 6.12.105 with commit 3855b6a11f8a7aceb8181cc08c99afef58517006 Issue introduced in 6.11 with commit c38fe1bb5d21c2ce0857965ee06174ee587d6b42 and fixed in 6.18.46 with commit 52a818c586ae2c36b7324bfaefb547f5e866a8ae Issue introduced in 6.11 with commit c38fe1bb5d21c2ce0857965ee06174ee587d6b42 and fixed in 7.1.10 with commit d38554602a0b04e85fad28ce72c7500cf50d419b Issue introduced in 6.11 with commit c38fe1bb5d21c2ce0857965ee06174ee587d6b42 and fixed in 7.2 with commit 7d5c576cb1c86047b1fcb1aa9532e17fc5e46c1d 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-2026-80575 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/input/misc/cs40l50-vibra.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/3855b6a11f8a7aceb8181cc08c99afef58517006 https://git.kernel.org/stable/c/52a818c586ae2c36b7324bfaefb547f5e866a8ae https://git.kernel.org/stable/c/d38554602a0b04e85fad28ce72c7500cf50d419b https://git.kernel.org/stable/c/7d5c576cb1c86047b1fcb1aa9532e17fc5e46c1d