linux-kernel - Re: [PATCH] ASoC: cs42l42: Prevent NULL pointer deref in interrupt handler

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: <163517996156.3558038.13466013835438231170.b4-ty@kernel.org>
Date:   Mon, 25 Oct 2021 17:39:24 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Richard Fitzgerald <rf@...nsource.cirrus.com>
Cc:     Mark Brown <broonie@...nel.org>, linux-kernel@...r.kernel.org,
        patches@...nsource.cirrus.com, alsa-devel@...a-project.org
Subject: Re: [PATCH] ASoC: cs42l42: Prevent NULL pointer deref in interrupt handler

On Mon, 25 Oct 2021 12:22:58 +0100, Richard Fitzgerald wrote:
> The interrupt handling code was getting the struct device* from a
> struct snd_soc_component* stored in struct cs42l42_private. If the
> interrupt was asserted before ASoC calls component_probe() the
> snd_soc_component* will be NULL.
> 
> The stored snd_soc_component* is not actually used for anything other
> than indirectly getting the struct device*. Remove it, and store the
> struct device* in struct cs42l42_private.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: cs42l42: Prevent NULL pointer deref in interrupt handler
      commit: 2003c44e28ac9759200a78dda20c5f695949e3f4

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