linux-kernel - Re: [PATCH next] spi: spi-qpic-snand: avoid memleak in qcom_spi_ecc_init_ctx

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: <174224057417.315737.5360981783264401396.b4-ty@kernel.org>
Date: Mon, 17 Mar 2025 19:42:54 +0000
From: Mark Brown <broonie@...nel.org>
To: Sricharan Ramabadhran <quic_srichara@...cinc.com>, 
 Md Sadre Alam <quic_mdalam@...cinc.com>, 
 Varadarajan Narayanan <quic_varada@...cinc.com>, 
 Gabor Juhos <j4g8y7@...il.com>
Cc: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH next] spi: spi-qpic-snand: avoid memleak in
 qcom_spi_ecc_init_ctx_pipelined()

On Thu, 13 Mar 2025 19:31:21 +0100, Gabor Juhos wrote:
> When the allocation of the OOB buffer fails, the
> qcom_spi_ecc_init_ctx_pipelined() function returns without freeing
> the memory allocated for 'ecc_cfg' thus it can cause a memory leak.
> 
> Call kfree() to free 'ecc_cfg' before returning from the function
> to avoid that.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: spi-qpic-snand: avoid memleak in qcom_spi_ecc_init_ctx_pipelined()
      commit: d450cdd9c4398add1f2aa7200f2c95f1e3b9f9fa

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