linux-kernel - Re: [v2 PATCH] ASoC: max98390: Fix potential crash during param fw loading

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: <159127965569.55652.8183322346754988005.b4-ty@kernel.org>
Date:   Thu, 04 Jun 2020 15:07:35 +0100
From:   Mark Brown <broonie@...nel.org>
To:     perex@...ex.cz, alsa-devel@...a-project.org,
        ckeepax@...nsource.cirrus.com,
        Steve Lee <steves.lee@...imintegrated.com>, nuno.sa@...log.com,
        rf@...nsource.wolfsonmicro.com, geert@...ux-m68k.org,
        shumingf@...ltek.com, linux-kernel@...r.kernel.org, tiwai@...e.com,
        krzk@...nel.org, jack.yu@...ltek.com, dmurphy@...com,
        lgirdwood@...il.com, srinivas.kandagatla@...aro.org
Cc:     ryan.lee.maxim@...il.com, steves.lee.maxim@...il.com,
        ryans.lee@...imintegrated.com
Subject: Re: [v2 PATCH] ASoC: max98390: Fix potential crash during param fw loading

On Thu, 4 Jun 2020 14:47:31 +0900, Steve Lee wrote:
>  malformed firmware file can cause out-of-bound access and crash
>  during dsm_param bin loading.
>   - add MIN/MAX param size to avoid out-of-bound access.
>   - read start addr and size of param and check bound.
>   - add condition that fw->size > param_size + _PAYLOAD_OFFSET
>     to confirm enough data.

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/1] ASoC: max98390: Fix potential crash during param fw loading
      commit: 97ed3e509ee6d098730d137759c627a8d674cf55

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