Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@kernel.org>
Cc: Hans de Goede <hdegoede@redhat.com>, linux-sound@vger.kernel.org
Subject: [PATCH 0/4] ASoC: Intel: byt*: Avoid OOB array read from the map name
Date: Tue, 15 Apr 2025 10:31:36 +0200	[thread overview]
Message-ID: <20250415083144.6588-1-tiwai@suse.de> (raw)

While reading bug reports, I casually stubmled on a UBSAN warning
about the array OOB access, and this looks like a real bug in ASoC
Intel driver code.  So here is a series of quick fixes for them.


Takashi

====

Takashi Iwai (4):
  ASoC: Intel: bytcht_es8316: Avoid OOB array read from the map name
  ASoC: Intel: bytcr_rt5640: Avoid OOB array read from the map name
  ASoC: Intel: bytcr_rt5651: Avoid OOB array read from the map name
  ASoC: Intel: bytcr_wm5102: Avoid OOB array read from the map name

 sound/soc/intel/boards/bytcht_es8316.c | 11 ++++++++---
 sound/soc/intel/boards/bytcr_rt5640.c  | 11 ++++++++---
 sound/soc/intel/boards/bytcr_rt5651.c  | 11 ++++++++---
 sound/soc/intel/boards/bytcr_wm5102.c  | 27 ++++++++++++++++++++------
 4 files changed, 45 insertions(+), 15 deletions(-)

-- 
2.49.0


             reply	other threads:[~2025-04-15  8:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-15  8:31 Takashi Iwai [this message]
2025-04-15  8:31 ` [PATCH 1/4] ASoC: Intel: bytcht_es8316: Avoid OOB array read from the map name Takashi Iwai
2025-04-15  8:31 ` [PATCH 2/4] ASoC: Intel: bytcr_rt5640: " Takashi Iwai
2025-04-15  8:31 ` [PATCH 3/4] ASoC: Intel: bytcr_rt5651: " Takashi Iwai
2025-04-15  8:31 ` [PATCH 4/4] ASoC: Intel: bytcr_wm5102: " Takashi Iwai
2025-04-15  9:12 ` [PATCH 0/4] ASoC: Intel: byt*: " Hans de Goede
2025-04-23 11:47   ` Takashi Iwai

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=20250415083144.6588-1-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=broonie@kernel.org \
    --cc=hdegoede@redhat.com \
    --cc=linux-sound@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