linux-kernel - Re: [PATCH] regulator: da9121: Fix uninit-value in da9121_assign_chip

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Thu, 21 Apr 2022 16:54:50 +0100
From:   Mark Brown <broonie@...nel.org>
To:     linux-kernel@...r.kernel.org, weiyongjun1@...wei.com
Cc:     support.opensource@...semi.com, lgirdwood@...il.com,
        Adam.Ward.opensource@...semi.com, hulkci@...wei.com
Subject: Re: [PATCH] regulator: da9121: Fix uninit-value in da9121_assign_chip_model()

On Thu, 21 Apr 2022 09:03:35 +0000, Wei Yongjun wrote:
> KASAN report slab-out-of-bounds in __regmap_init as follows:
> 
> BUG: KASAN: slab-out-of-bounds in __regmap_init drivers/base/regmap/regmap.c:841
> Read of size 1 at addr ffff88803678cdf1 by task xrun/9137
> 
> CPU: 0 PID: 9137 Comm: xrun Tainted: G        W         5.18.0-rc2
> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014
> Call Trace:
>  <TASK>
>  dump_stack_lvl+0xe8/0x15a lib/dump_stack.c:88
>  print_report.cold+0xcd/0x69b mm/kasan/report.c:313
>  kasan_report+0x8e/0xc0 mm/kasan/report.c:491
>  __regmap_init+0x4540/0x4ba0 drivers/base/regmap/regmap.c:841
>  __devm_regmap_init+0x7a/0x100 drivers/base/regmap/regmap.c:1266
>  __devm_regmap_init_i2c+0x65/0x80 drivers/base/regmap/regmap-i2c.c:394
>  da9121_i2c_probe+0x386/0x6d1 drivers/regulator/da9121-regulator.c:1039
>  i2c_device_probe+0x959/0xac0 drivers/i2c/i2c-core-base.c:563
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: da9121: Fix uninit-value in da9121_assign_chip_model()
      commit: bab76514aca36bc513224525d5598da676938218

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