linux-kernel - Re: [PATCH][next] ASoC: qcom: add missing out of memory check on drvdata->clks allocation

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: <159796008815.44152.14467897806901945440.b4-ty@kernel.org>
Date:   Thu, 20 Aug 2020 22:48:12 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Patrick Lai <plai@...eaurora.org>,
        Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
        alsa-devel@...a-project.org, Colin King <colin.king@...onical.com>,
        Jaroslav Kysela <perex@...ex.cz>,
        Banajit Goswami <bgoswami@...eaurora.org>,
        Takashi Iwai <tiwai@...e.com>,
        Ajit Pandey <ajitp@...eaurora.org>,
        Liam Girdwood <lgirdwood@...il.com>,
        Rohit kumar <rohitkr@...eaurora.org>
Cc:     linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org
Subject: Re: [PATCH][next] ASoC: qcom: add missing out of memory check on drvdata->clks allocation

On Wed, 19 Aug 2020 17:01:03 +0100, Colin King wrote:
> Currently drvdata->clks is not being checked for an allocation failure,
> leading to potential null pointer dereferencing. Fix this by adding a
> check and returning -ENOMEM if an error occurred.

Applied to

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

Thanks!

[1/1] ASoC: qcom: add missing out of memory check on drvdata->clks allocation
      commit: a467f2f8ad5f9a21f92b3fa6ad2aac90fa7054fe

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