Answer in brief
CVE-2026-43461 records a Unknown severity vulnerability in spi: amlogic: spifc-a4: Fix DMA mapping error handling. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=4670db6f32e9379f5ab6c9bb2a6787cd9b9230a9 <0a83d6c9e149a176340190fa9cbadf2266db4c9a || >=4670db6f32e9379f5ab6c9bb2a6787cd9b9230a9 <c0b88f1176074f80140ed77fce909f254b7180ab || >=4670db6f32e9379f5ab6c9bb2a6787cd9b9230a9 <b20b437666e1cb26a7c499d1664e8f2a0ac67000 | 0a83d6c9e149a176340190fa9cbadf2266db4c9a, c0b88f1176074f80140ed77fce909f254b7180ab, b20b437666e1cb26a7c499d1664e8f2a0ac67000 |
| Linux/Linuxgeneric | 6.18 | Not reported |
Published upstream
May 8, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-43461 records a Unknown severity vulnerability in spi: amlogic: spifc-a4: Fix DMA mapping error handling. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=4670db6f32e9379f5ab6c9bb2a6787cd9b9230a9 <0a83d6c9e149a176340190fa9cbadf2266db4c9a || >=4670db6f32e9379f5ab6c9bb2a6787cd9b9230a9 <c0b88f1176074f80140ed77fce909f254b7180ab || >=4670db6f32e9379f5ab6c9bb2a6787cd9b9230a9 <b20b437666e1cb26a7c499d1664e8f2a0ac67000 | 0a83d6c9e149a176340190fa9cbadf2266db4c9a, c0b88f1176074f80140ed77fce909f254b7180ab, b20b437666e1cb26a7c499d1664e8f2a0ac67000 |
| Linux/Linuxgeneric | 6.18 | Not reported |
Published upstream
May 8, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.