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.
Security readout for executives and security teams
Plain-English summary
A Linux driver for the Amlogic A4 SPI flash controller mishandles failures while preparing DMA transfers. The errors can cause duplicate cleanup or use the wrong buffer size, potentially affecting system confidentiality, integrity, and availability. Risk is limited to systems using the relevant hardware and driver path.
Executive priority
Treat as a high-priority, hardware-scoped kernel update. Rapidly identify affected Amlogic-based appliances or embedded systems, then patch through supported vendor channels. Broad emergency action is not supported for systems lacking the relevant controller or driver.
Technical view
The vulnerability is in aml_sfc_dma_buffer_setup() within the Amlogic spifc-a4 SPI driver. Its DMA-mapping error paths could double-unmap sfc->daddr and unmap sfc->iaddr using datalen instead of infolen. The published CVSS 3.1 score is 7.8, reflecting a local, low-privilege attack requiring no user interaction.
Likely exposure
Likely exposure is concentrated in Linux systems using the Amlogic A4 SPI flash controller and affected spifc-a4 driver versions. The supplied record names releases including 6.18, 6.18.19, 6.19.9, and 7.0, but does not clearly express complete version boundaries.
Exploitation context
The supplied record does not identify public exploitation, and the CVE is not listed as KEV. The CVSS vector describes local access with low privileges. No remote attack path or exploit method is established by the provided sources.
Researcher notes
The primary defects are error-path resource-management mistakes: a double DMA unmap and an incorrect unmap length. The supplied references provide three stable-tree fixes, but do not map each commit to explicit release branches. Evidence is insufficient to characterize exploitability beyond the published local CVSS assessment.
Mitigation direction
Apply a vendor-supported kernel update containing the applicable linked stable fix.
Check distribution or device-vendor guidance for precise affected and fixed package versions.
Prioritize systems confirmed to use the Amlogic A4 SPI controller and spifc-a4 driver.
Monitor upstream and vendor advisories because the supplied version boundaries are incomplete.
Validation and detection
Inventory kernel versions on devices containing Amlogic A4 hardware.
Confirm whether the spifc-a4 driver is present and used by the deployed system.
Verify the installed kernel includes the applicable linked stable commit.
After updating, run normal SPI storage and platform regression testing.
Review vendor advisories to confirm package-level remediation status.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-43461 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
4Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.