CVE-2026-43461: spi: amlogic: spifc-a4: Fix DMA mapping error handling

CVE-2026-43461: spi: amlogic: spifc-a4: Fix DMA mapping error handling

[Greg Kroah-Hartman]

From: Greg Kroah-Hartman <gregkh@kernel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

spi: amlogic: spifc-a4: Fix DMA mapping error handling

Fix three bugs in aml_sfc_dma_buffer_setup() error paths:
1. Unnecessary goto: When the first DMA mapping (sfc->daddr) fails,
   nothing needs cleanup. Use direct return instead of goto.
2. Double-unmap bug: When info DMA mapping failed, the code would
   unmap sfc->daddr inline, then fall through to out_map_data which
   would unmap it again, causing a double-unmap.
3. Wrong unmap size: The out_map_info label used datalen instead of
   infolen when unmapping sfc->iaddr, which could lead to incorrect
   DMA sync behavior.

The Linux kernel CVE team has assigned CVE-2026-43461 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 6.18 with commit 4670db6f32e9379f5ab6c9bb2a6787cd9b9230a9 and fixed in 6.18.19 with commit 0a83d6c9e149a176340190fa9cbadf2266db4c9a
	Issue introduced in 6.18 with commit 4670db6f32e9379f5ab6c9bb2a6787cd9b9230a9 and fixed in 6.19.9 with commit c0b88f1176074f80140ed77fce909f254b7180ab
	Issue introduced in 6.18 with commit 4670db6f32e9379f5ab6c9bb2a6787cd9b9230a9 and fixed in 7.0 with commit b20b437666e1cb26a7c499d1664e8f2a0ac67000

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2026-43461
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	drivers/spi/spi-amlogic-spifc-a4.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/0a83d6c9e149a176340190fa9cbadf2266db4c9a
	https://git.kernel.org/stable/c/c0b88f1176074f80140ed77fce909f254b7180ab
	https://git.kernel.org/stable/c/b20b437666e1cb26a7c499d1664e8f2a0ac67000