Files
vuln-cve/data/2026/43xxx/CVE-2026-43461.json
T

159 lines
8.3 KiB
JSON
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
{
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"cveMetadata": {
"cveId": "CVE-2026-43461",
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"state": "PUBLISHED",
"assignerShortName": "Linux",
"dateReserved": "2026-05-01T14:12:56.010Z",
"datePublished": "2026-05-08T14:22:23.999Z",
"dateUpdated": "2026-08-05T12:28:05.393Z"
},
"containers": {
"cna": {
"providerMetadata": {
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux",
"dateUpdated": "2026-08-05T12:28:05.393Z"
},
"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->daddr) 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->daddr 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->iaddr, which could lead to incorrect\n DMA sync behavior."
}
],
"metrics": [
{
"cvssV3_1": {
"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"
},
"scenarios": [
{
"lang": "en",
"value": "AV:L - The vulnerable path is reached through local storage I/O to an Amlogic SPI-NAND/SPI-NOR controller via MTD/SPI-mem operations, not through an in-kernel network protocol.\nAC:L - There is no race to win; an attacker who can cause repeated flash reads/writes can exercise the DMA mapping error paths, and uncertainty about inducing mapping failure is resolved toward the higher-severity low-complexity value.\nPR:L - A low-privileged local user can plausibly trigger flash-backed filesystem or MTD read paths on affected embedded systems without kernel capabilities, even though direct raw MTD writes may be further restricted.\nUI:N - Exploitation is initiated by the attacker’s own local I/O and does not require a separate victim action.\nS:U - The impact remains within the kernel and device DMA management security authority; this is not a VM escape or crossing into a different authorization scope.\nC:H - The bad cleanup can double-unmap or over-unmap DMA/IOMMU mappings, plausibly creating stale or overlapping DMA mappings that can expose kernel memory.\nI:H - Corrupt DMA mapping bookkeeping can plausibly allow DMA aliasing or writes into unintended kernel memory, so integrity impact is high under the required higher-severity rule.\nA:H - Invalid, double, or wrong-sized DMA unmaps can trigger warnings, IOMMU/DMA allocator corruption, or crashes/hangs in kernel I/O paths."
}
]
}
],
"affected": [
{
"product": "Linux",
"vendor": "Linux",
"defaultStatus": "unaffected",
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"programFiles": [
"drivers/spi/spi-amlogic-spifc-a4.c"
],
"versions": [
{
"version": "4670db6f32e9379f5ab6c9bb2a6787cd9b9230a9",
"lessThan": "0a83d6c9e149a176340190fa9cbadf2266db4c9a",
"status": "affected",
"versionType": "git"
},
{
"version": "4670db6f32e9379f5ab6c9bb2a6787cd9b9230a9",
"lessThan": "c0b88f1176074f80140ed77fce909f254b7180ab",
"status": "affected",
"versionType": "git"
},
{
"version": "4670db6f32e9379f5ab6c9bb2a6787cd9b9230a9",
"lessThan": "b20b437666e1cb26a7c499d1664e8f2a0ac67000",
"status": "affected",
"versionType": "git"
}
]
},
{
"product": "Linux",
"vendor": "Linux",
"defaultStatus": "affected",
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"programFiles": [
"drivers/spi/spi-amlogic-spifc-a4.c"
],
"versions": [
{
"version": "6.18",
"status": "affected"
},
{
"version": "0",
"lessThan": "6.18",
"status": "unaffected",
"versionType": "semver"
},
{
"version": "6.18.19",
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"versionType": "semver"
},
{
"version": "6.19.9",
"lessThanOrEqual": "6.19.*",
"status": "unaffected",
"versionType": "semver"
},
{
"version": "7.0",
"lessThanOrEqual": "*",
"status": "unaffected",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"operator": "OR",
"negate": false,
"cpeMatch": [
{
"vulnerable": true,
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionStartIncluding": "6.18",
"versionEndExcluding": "6.18.19"
},
{
"vulnerable": true,
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionStartIncluding": "6.18",
"versionEndExcluding": "6.19.9"
},
{
"vulnerable": true,
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionStartIncluding": "6.18",
"versionEndExcluding": "7.0"
}
]
}
]
}
],
"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"
}
}
}
}