linux-kernel - Re: [PATCH] spi: mpc52xx: Add cancel_work

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: <173314624184.54221.7774657892110514848.b4-ty@kernel.org>
Date: Mon, 02 Dec 2024 13:30:41 +0000
From: Mark Brown <broonie@...nel.org>
To: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org, 
 Pei Xiao <xiaopei01@...inos.cn>
Subject: Re: [PATCH] spi: mpc52xx: Add cancel_work_sync before module
 remove

On Thu, 28 Nov 2024 16:38:17 +0800, Pei Xiao wrote:
> If we remove the module which will call mpc52xx_spi_remove
> it will free 'ms' through spi_unregister_controller.
> while the work ms->work will be used. The sequence of operations
> that may lead to a UAF bug.
> 
> Fix it by ensuring that the work is canceled before proceeding with
> the cleanup in mpc52xx_spi_remove.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: mpc52xx: Add cancel_work_sync before module remove
      commit: 984836621aad98802d92c4a3047114cf518074c8

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