CVE-2026-43461

Analyzed Analyzed - Analysis Complete

spi: amlogic spifc-a4 DMA mapping error handling fix

Publication date: 2026-05-08

Last updated on: 2026-05-20

Assigner: 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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-05-08

Last Modified

2026-05-20

Generated

2026-07-09

AI Q&A

2026-05-08

EPSS Evaluated

2026-07-08

NVD

CVE-2026-43461

EUVD

EUVD-2026-28767

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	7.0
linux	linux_kernel	7.0
linux	linux_kernel	7.0
linux	linux_kernel	From 6.19 (inc) to 6.19.9 (exc)
linux	linux_kernel	From 6.18 (inc) to 6.18.19 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-UNKNOWN

Attack-Flow Graph

Executive Summary

This vulnerability is related to the Linux kernel's amlogic spifc-a4 driver, specifically in the DMA (Direct Memory Access) mapping error handling within the aml_sfc_dma_buffer_setup() function.

There was an unnecessary use of a goto statement when the first DMA mapping failed, which should have been a direct return instead.
A double-unmap bug occurred where the code would unmap the same DMA address twice if the info DMA mapping failed.
An incorrect unmap size was used in one error path, potentially causing incorrect DMA synchronization behavior.

These bugs have been fixed to ensure proper error handling and resource cleanup in the DMA mapping process.

Impact Analysis

Improper handling of DMA mapping errors can lead to resource mismanagement such as double unmapping or incorrect synchronization, which may cause system instability or crashes.

While the description does not specify direct security impacts like privilege escalation or data leakage, such bugs in kernel drivers can potentially lead to unpredictable behavior affecting system reliability.

Hi! I’m here to help you understand CVE-2026-43461. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70