linux-kernel - Re: [PATCH] spi: mchp-pci1xxx: Fix a possible null pointer dereference in pci1xxx_spi

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, 03 Apr 2024 14:32:45 +0100
From: Mark Brown <broonie@...nel.org>
To: Huai-Yuan Liu <qq810974084@...il.com>
Cc: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org, 
 baijiaju1990@...look.com
Subject: Re: [PATCH] spi: mchp-pci1xxx: Fix a possible null pointer
 dereference in pci1xxx_spi_probe

On Wed, 03 Apr 2024 09:42:21 +0800, Huai-Yuan Liu wrote:
> In function pci1xxxx_spi_probe, there is a potential null pointer that
> may be caused by a failed memory allocation by the function devm_kzalloc.
> Hence, a null pointer check needs to be added to prevent null pointer
> dereferencing later in the code.
> 
> To fix this issue, spi_bus->spi_int[iter] should be checked. The memory
> allocated by devm_kzalloc will be automatically released, so just directly
> return -ENOMEM without worrying about memory leaks.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: mchp-pci1xxx: Fix a possible null pointer dereference in pci1xxx_spi_probe
      commit: 1f886a7bfb3faf4c1021e73f045538008ce7634e

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