Linux Input/HID development
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: HyeongJun An <sammiee5311@gmail.com>
Cc: James Ogletree <jogletre@opensource.cirrus.com>,
	 Fred Treven <fred.treven@cirrus.com>,
	Ben Bright <ben.bright@cirrus.com>,
	 patches@opensource.cirrus.com, linux-input@vger.kernel.org,
	linux-kernel@vger.kernel.org,  stable@vger.kernel.org
Subject: Re: [PATCH] Input: cs40l50-vibra - validate custom data from user space
Date: Fri, 24 Jul 2026 16:48:40 -0700	[thread overview]
Message-ID: <amP5s-Dzp9_qWxAd@google.com> (raw)
In-Reply-To: <20260718074032.1864861-1-sammiee5311@gmail.com>

On Sat, Jul 18, 2026 at 04:40:32PM +0900, HyeongJun An wrote:
> 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.
> 
> Fixes: c38fe1bb5d21 ("Input: cs40l50 - Add support for the CS40L50 haptic driver")
> Cc: stable@vger.kernel.org
> Assisted-by: Claude:claude-opus-4-8
> Signed-off-by: HyeongJun An <sammiee5311@gmail.com>

Applied, thank you.

-- 
Dmitry

      parent reply	other threads:[~2026-07-24 23:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-18  7:40 [PATCH] Input: cs40l50-vibra - validate custom data from user space HyeongJun An
2026-07-18  7:54 ` sashiko-bot
2026-07-24 23:48 ` Dmitry Torokhov [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=amP5s-Dzp9_qWxAd@google.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=ben.bright@cirrus.com \
    --cc=fred.treven@cirrus.com \
    --cc=jogletre@opensource.cirrus.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@opensource.cirrus.com \
    --cc=sammiee5311@gmail.com \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox