linux-kernel - Re: [PATCH v2] ASoC: Intel: sof_rt5682: fix out-of-bounds array access

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <165671411147.591936.521859286196210706.b4-ty@kernel.org>
Date:   Fri, 01 Jul 2022 23:21:51 +0100
From:   Mark Brown <broonie@...nel.org>
To:     alsa-devel@...a-project.org, brent.lu@...el.com
Cc:     linux-kernel@...r.kernel.org, peter.ujfalusi@...ux.intel.com,
        yong.zhi@...el.com, liam.r.girdwood@...ux.intel.com,
        cezary.rojewski@...el.com, perex@...ex.cz, ajye.huang@...il.com,
        tiwai@...e.com, ranjani.sridharan@...ux.intel.com,
        mac.chiang@...el.com, kai.vehmanen@...ux.intel.com,
        yung-chuan.liao@...ux.intel.com,
        pierre-louis.bossart@...ux.intel.com
Subject: Re: [PATCH v2] ASoC: Intel: sof_rt5682: fix out-of-bounds array access

On Fri, 1 Jul 2022 22:15:17 +0800, Brent Lu wrote:
> Starting from ADL platform we have four HDMI PCM devices which exceeds
> the size of sof_hdmi array. Since each sof_hdmi_pcm structure
> represents one HDMI PCM device, we remove the sof_hdmi array and add a
> new member hdmi_jack to the sof_hdmi_pcm structure to fix the
> out-of-bounds problem.
> 
> 
> [...]

Applied to

   broonie/sound.git for-linus

Thanks!

[1/1] ASoC: Intel: sof_rt5682: fix out-of-bounds array access
      commit: fba5a02a4c028dad32299aa723716349f93845eb

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark