linux-kernel - Re: [PATCH] spi: tegra20-slink: fix UAF in tegra_slink

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]

Date:   Wed, 13 Jul 2022 15:19:53 +0100
From:   Mark Brown <broonie@...nel.org>
To:     linux-tegra@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-spi@...r.kernel.org, yangyingliang@...wei.com
Cc:     digetx@...il.com
Subject: Re: [PATCH] spi: tegra20-slink: fix UAF in tegra_slink_remove()

On Wed, 13 Jul 2022 17:40:23 +0800, Yang Yingliang wrote:
> After calling spi_unregister_master(), the refcount of master will
> be decrease to 0, and it will be freed in spi_controller_release(),
> the device data also will be freed, so it will lead a UAF when using
> 'tspi'. To fix this, get the master before unregister and put it when
> finish using it.
> 
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: tegra20-slink: fix UAF in tegra_slink_remove()
      commit: 7e9984d183bb1e99e766c5c2b950ff21f7f7b6c0

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