Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
Cc: perex@perex.cz, tiwai@suse.com, linux-sound@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH] ALSA: hda/hdmi: clamp num_cvts against cvt_nids[] in hdmi_read_pin_conn
Date: Thu, 08 Oct 2026 12:11:04 +0200	[thread overview]
Message-ID: <87ld885wp3.wl-tiwai@suse.de> (raw)
In-Reply-To: <20261008085122.9442-1-peter.ujfalusi@linux.intel.com>

On Thu, 08 Oct 2026 10:51:22 +0200,
Peter Ujfalusi wrote:
> 
> hdmi_add_cvt() stores each converter's NID into the fixed-size
> spec->cvt_nids[] array (used only by the Intel Haswell pin-connection
> fixup), but only when spec->num_cvts is still within
> ARRAY_SIZE(cvt_nids); the num_cvts counter itself is incremented
> unconditionally regardless of whether the store happened. A codec
> that reports more converters than cvt_nids[] can hold therefore ends
> up with num_cvts > ARRAY_SIZE(cvt_nids).
> 
> hdmi_read_pin_conn(), on the intel_hsw_fixup path, copies num_cvts
> elements from cvt_nids[] with memcpy(), so once num_cvts exceeds the
> array size this reads past cvt_nids[] and writes the resulting
> garbage NIDs into per_pin->mux_nids[].
> 
> Clamp the copy length to the actual size of cvt_nids[] instead of
> trusting num_cvts, which is also used unbounded as the size of the
> separate, dynamically-sized spec->cvts array and must not be
> truncated at the source.
> 
> Fixes: bce0d2a80e42 ("ALSA: hda - Allow unlimited pins and converters in patch_hdmi.c")
> Cc: stable@vger.kernel.org
> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>

Applied to for-next branch.  Thanks.


Takashi

      reply	other threads:[~2026-10-08 10:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-08  8:51 [PATCH] ALSA: hda/hdmi: clamp num_cvts against cvt_nids[] in hdmi_read_pin_conn Peter Ujfalusi
2026-10-08 10:11 ` Takashi Iwai [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=87ld885wp3.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=peter.ujfalusi@linux.intel.com \
    --cc=stable@vger.kernel.org \
    --cc=tiwai@suse.com \
    /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