linux-kernel - Re: [PATCH] spi: Ensure that sg_table won't be used after being freed

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: <166454276436.255916.3302149825937071589.b4-ty@kernel.org>
Date:   Fri, 30 Sep 2022 13:59:24 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Marek Szyprowski <m.szyprowski@...sung.com>,
        linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org
Cc:     Vincent Whitchurch <vincent.whitchurch@...s.com>
Subject: Re: [PATCH] spi: Ensure that sg_table won't be used after being freed

On Fri, 30 Sep 2022 13:34:08 +0200, Marek Szyprowski wrote:
> SPI code checks for non-zero sgt->orig_nents to determine if the buffer
> has been DMA-mapped. Ensure that sg_table is really zeroed after free to
> avoid potential NULL pointer dereference if the given SPI xfer object is
> reused again without being DMA-mapped.
> 
> 

Applied to

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

Thanks!

[1/1] spi: Ensure that sg_table won't be used after being freed
      commit: 8e9204cddcc3fea9affcfa411715ba4f66e97587

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