CVE-2026-43461 (GCVE-0-2026-43461)
Vulnerability from cvelistv5 – Published: 2026-05-08 14:22 – Updated: 2026-05-11 22:25
VLAI?
Title
spi: amlogic: spifc-a4: Fix DMA mapping error handling
Summary
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.
Severity ?
7.8 (High)
Assigner
References
Impacted products
2 products
| Vendor | Product | Version | |
|---|---|---|---|
| Linux | Linux |
Affected:
4670db6f32e9379f5ab6c9bb2a6787cd9b9230a9 , < 0a83d6c9e149a176340190fa9cbadf2266db4c9a
(git)
Affected: 4670db6f32e9379f5ab6c9bb2a6787cd9b9230a9 , < c0b88f1176074f80140ed77fce909f254b7180ab (git) Affected: 4670db6f32e9379f5ab6c9bb2a6787cd9b9230a9 , < b20b437666e1cb26a7c499d1664e8f2a0ac67000 (git) |
|
| Linux | Linux |
Affected:
6.18
Unaffected: 0 , < 6.18 (semver) Unaffected: 6.18.19 , ≤ 6.18.* (semver) Unaffected: 6.19.9 , ≤ 6.19.* (semver) Unaffected: 7.0 , ≤ * (original_commit_for_fix) |
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/spi/spi-amlogic-spifc-a4.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "0a83d6c9e149a176340190fa9cbadf2266db4c9a",
"status": "affected",
"version": "4670db6f32e9379f5ab6c9bb2a6787cd9b9230a9",
"versionType": "git"
},
{
"lessThan": "c0b88f1176074f80140ed77fce909f254b7180ab",
"status": "affected",
"version": "4670db6f32e9379f5ab6c9bb2a6787cd9b9230a9",
"versionType": "git"
},
{
"lessThan": "b20b437666e1cb26a7c499d1664e8f2a0ac67000",
"status": "affected",
"version": "4670db6f32e9379f5ab6c9bb2a6787cd9b9230a9",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/spi/spi-amlogic-spifc-a4.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.18"
},
{
"lessThan": "6.18",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.19",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.19.*",
"status": "unaffected",
"version": "6.19.9",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.0",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.19",
"versionStartIncluding": "6.18",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.19.9",
"versionStartIncluding": "6.18",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.0",
"versionStartIncluding": "6.18",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nspi: amlogic: spifc-a4: Fix DMA mapping error handling\n\nFix three bugs in aml_sfc_dma_buffer_setup() error paths:\n1. Unnecessary goto: When the first DMA mapping (sfc-\u003edaddr) fails,\n nothing needs cleanup. Use direct return instead of goto.\n2. Double-unmap bug: When info DMA mapping failed, the code would\n unmap sfc-\u003edaddr inline, then fall through to out_map_data which\n would unmap it again, causing a double-unmap.\n3. Wrong unmap size: The out_map_info label used datalen instead of\n infolen when unmapping sfc-\u003eiaddr, which could lead to incorrect\n DMA sync behavior."
}
],
"metrics": [
{
"cvssV3_1": {
"baseScore": 7.8,
"baseSeverity": "HIGH",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-05-11T22:25:02.472Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/0a83d6c9e149a176340190fa9cbadf2266db4c9a"
},
{
"url": "https://git.kernel.org/stable/c/c0b88f1176074f80140ed77fce909f254b7180ab"
},
{
"url": "https://git.kernel.org/stable/c/b20b437666e1cb26a7c499d1664e8f2a0ac67000"
}
],
"title": "spi: amlogic: spifc-a4: Fix DMA mapping error handling",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-43461",
"datePublished": "2026-05-08T14:22:23.999Z",
"dateReserved": "2026-05-01T14:12:56.010Z",
"dateUpdated": "2026-05-11T22:25:02.472Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-43461",
"date": "2026-05-19",
"epss": "0.00013",
"percentile": "0.02188"
},
"nvd": "{\"cve\":{\"id\":\"CVE-2026-43461\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2026-05-08T15:16:58.977\",\"lastModified\":\"2026-05-12T14:10:27.343\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nspi: amlogic: spifc-a4: Fix DMA mapping error handling\\n\\nFix three bugs in aml_sfc_dma_buffer_setup() error paths:\\n1. Unnecessary goto: When the first DMA mapping (sfc-\u003edaddr) fails,\\n nothing needs cleanup. Use direct return instead of goto.\\n2. Double-unmap bug: When info DMA mapping failed, the code would\\n unmap sfc-\u003edaddr inline, then fall through to out_map_data which\\n would unmap it again, causing a double-unmap.\\n3. Wrong unmap size: The out_map_info label used datalen instead of\\n infolen when unmapping sfc-\u003eiaddr, which could lead to incorrect\\n DMA sync behavior.\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\",\"baseScore\":7.8,\"baseSeverity\":\"HIGH\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"HIGH\",\"integrityImpact\":\"HIGH\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":1.8,\"impactScore\":5.9}]},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/0a83d6c9e149a176340190fa9cbadf2266db4c9a\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/b20b437666e1cb26a7c499d1664e8f2a0ac67000\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/c0b88f1176074f80140ed77fce909f254b7180ab\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
}
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…