Re: [PATCH] regulator: core: fix UAF in destroy_regulator()

[Mark Brown]

On Wed, 16 Nov 2022 11:37:06 +0800, Yang Yingliang wrote:
> I got a UAF report as following:
> 
> ==================================================================
> BUG: KASAN: use-after-free in __lock_acquire+0x935/0x2060
> Read of size 8 at addr ffff88810e838220 by task python3/268
> Call Trace:
>  <TASK>
>  dump_stack_lvl+0x67/0x83
>  print_report+0x178/0x4b0
>  kasan_report+0x90/0x190
>  __lock_acquire+0x935/0x2060
>  lock_acquire+0x156/0x400
>  _raw_spin_lock+0x2a/0x40
>  lockref_get+0x11/0x30
>  simple_recursive_removal+0x41/0x440
>  debugfs_remove.part.12+0x32/0x50
>  debugfs_remove+0x29/0x30
>  _regulator_put.cold.54+0x3e/0x27f
>  regulator_put+0x1f/0x30
>  release_nodes+0x6a/0xa0
>  devres_release_all+0xf8/0x150
> 
> [...]

Applied to

   broonie/regulator.git for-next

Thanks!

[1/1] regulator: core: fix UAF in destroy_regulator()
      commit: 1f386d6894d0f1b7de8ef640c41622ddd698e7ab

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