From: Vinod Koul <vkoul@kernel.org>
To: Bard Liao <yung-chuan.liao@linux.intel.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>,
Jaroslav Kysela <perex@perex.cz>,
Baoli Zhang <baoli.zhang@linux.intel.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND v1 1/3] soundwire: fix bug in sdw_add_element_group_count found by syzkaller
Date: Thu, 07 May 2026 13:11:28 +0530 [thread overview]
Message-ID: <177813968854.210449.8596023623305001825.b4-ty@kernel.org> (raw)
In-Reply-To: <20260506055039.3751028-2-baoli.zhang@linux.intel.com>
On Wed, 06 May 2026 13:50:35 +0800, Baoli Zhang wrote:
> The original implementation caused an out-of-bounds memory access
> in the sdw_add_element_group_count for-loop when i == num.
>
> for (i = 0; i <= num; i++) {
> if (rate == group->rates[i] && lane == group->lanes[i])
> ...
>
> [...]
Applied, thanks!
[1/3] soundwire: fix bug in sdw_add_element_group_count found by syzkaller
commit: f772ff5a0e6758fd412803c09e03ba3bca5f5878
[2/3] soundwire: increase group->max_size after allocation
commit: 654a7ae10b2ee6b07d5d9193c1c5465410781908
[3/3] soundwire: use krealloc_array to prevent integer overflow
commit: 35a5ab8ef7f0f00b30eab9d917f3f0f4a2bec5d6
Best regards,
--
~Vinod
next prev parent reply other threads:[~2026-05-07 7:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260506055039.3751028-1-baoli.zhang@linux.intel.com>
2026-05-06 5:50 ` [PATCH RESEND v1 1/3] soundwire: fix bug in sdw_add_element_group_count found by syzkaller Baoli Zhang
2026-05-07 7:41 ` Vinod Koul [this message]
2026-05-06 5:50 ` [PATCH RESEND v1 2/3] soundwire: increase group->max_size after allocation Baoli Zhang
2026-05-06 5:50 ` [PATCH RESEND v1 3/3] soundwire: use krealloc_array to prevent integer overflow Baoli Zhang
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=177813968854.210449.8596023623305001825.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=baoli.zhang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.dev \
--cc=yung-chuan.liao@linux.intel.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