Files
vuln-cve/data/2024/58xxx/CVE-2024-58075.json
T

161 lines
9.3 KiB
JSON

{
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"cveMetadata": {
"cveId": "CVE-2024-58075",
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"state": "PUBLISHED",
"assignerShortName": "Linux",
"dateReserved": "2025-03-06T15:52:09.182Z",
"datePublished": "2025-03-06T16:04:30.864Z",
"dateUpdated": "2026-08-05T11:47:34.129Z"
},
"containers": {
"cna": {
"providerMetadata": {
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux",
"dateUpdated": "2026-08-05T11:47:34.129Z"
},
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: tegra - do not transfer req when tegra init fails\n\nThe tegra_cmac_init or tegra_sha_init function may return an error when\nmemory is exhausted. It should not transfer the request when they return\nan error."
}
],
"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 `tegra_sha_digest()`/`tegra_cmac_digest()` entry points are reached from local userspace via an AF_ALG hash socket (`crypto/algif_hash.c:137` calls `crypto_ahash_digest()`), requiring local system access rather than network reachability. In-kernel consumers such as IPsec `authenc`/AH also reach `.digest`, but the primary and reliable vector is a local syscall sequence.\nAC:L - The only precondition is a `dma_alloc_coherent()` failure, and an unprivileged attacker can create that condition themselves by exhausting and fragmenting memory while looping `send()` on the AF_ALG socket, so both sides of the condition are under attacker control. The attacker also fully controls the algorithm, buffer length and data that get written through the bad pointer.\nPR:L - AF_ALG socket creation and `hash` binding require no capability, so any unprivileged local user or containerized process can invoke the digest path. No CAP_SYS_ADMIN, root, or namespace trick is needed.\nUI:N - The attacker performs the entire sequence — socket/bind/accept/send under self-induced memory pressure — with no action by any other user or administrator.\nS:U - The corruption occurs in kernel memory belonging to the same security authority as the exploiting process; there is no crossing of a VM, hypervisor, or IOMMU boundary. The SE hardware DMA remains behind the SoC's SMMU.\nC:H - The failed-init paths leave `residue.buf`/`datbuf.buf` as dangling-freed or uninitialized stale heap pointers that are subsequently read (`memcpy(rctx->datbuf.buf, rctx->residue.buf, ...)` in `tegra_*_do_final()`) and used as DMA handles for the security engine, and the resulting digest is returned to userspace. This use-after-free/wild-read gives kernel memory disclosure and is leveragable for broader information leak.\nI:H - `tegra_sha_do_update()`/`tegra_cmac_do_update()` write attacker-supplied message bytes of attacker-chosen length through a freed or stale-heap pointer via `scatterwalk_map_and_copy()`, and `tegra_sha_init()`'s `resbuf_fail` path additionally calls `dma_free_coherent()` on an uninitialized pointer. A groomable UAF/wild-write with controlled contents is an arbitrary-write primitive suitable for control-flow hijack.\nA:H - In the common case `datbuf.buf` or `residue.buf` is NULL and the update/final handlers `memcpy()` through it, producing an immediate kernel oops inside the crypto engine kthread; the wild `dma_free_coherent()` and freed-DMA-buffer writes likewise panic the machine. The condition is repeatable at will by an unprivileged user."
}
]
}
],
"affected": [
{
"product": "Linux",
"vendor": "Linux",
"defaultStatus": "unaffected",
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"programFiles": [
"drivers/crypto/tegra/tegra-se-aes.c",
"drivers/crypto/tegra/tegra-se-hash.c"
],
"versions": [
{
"version": "0880bb3b00c855fc244b7177ffdaafef4d0aa1e0",
"lessThan": "1dbc270f9df7f0ae1e591323431869059cee1b7d",
"status": "affected",
"versionType": "git"
},
{
"version": "0880bb3b00c855fc244b7177ffdaafef4d0aa1e0",
"lessThan": "5eaa7c916e1ec4b122a1c3a8a20e692d9d9e174e",
"status": "affected",
"versionType": "git"
},
{
"version": "0880bb3b00c855fc244b7177ffdaafef4d0aa1e0",
"lessThan": "15589bda46830695a3261518bb7627afac61f519",
"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/crypto/tegra/tegra-se-aes.c",
"drivers/crypto/tegra/tegra-se-hash.c"
],
"versions": [
{
"version": "6.10",
"status": "affected"
},
{
"version": "0",
"lessThan": "6.10",
"status": "unaffected",
"versionType": "semver"
},
{
"version": "6.12.13",
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"versionType": "semver"
},
{
"version": "6.13.2",
"lessThanOrEqual": "6.13.*",
"status": "unaffected",
"versionType": "semver"
},
{
"version": "6.14",
"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.10",
"versionEndExcluding": "6.12.13"
},
{
"vulnerable": true,
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionStartIncluding": "6.10",
"versionEndExcluding": "6.13.2"
},
{
"vulnerable": true,
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionStartIncluding": "6.10",
"versionEndExcluding": "6.14"
}
]
}
]
}
],
"references": [
{
"url": "https://git.kernel.org/stable/c/1dbc270f9df7f0ae1e591323431869059cee1b7d"
},
{
"url": "https://git.kernel.org/stable/c/5eaa7c916e1ec4b122a1c3a8a20e692d9d9e174e"
},
{
"url": "https://git.kernel.org/stable/c/15589bda46830695a3261518bb7627afac61f519"
}
],
"title": "crypto: tegra - do not transfer req when tegra init fails",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
}
}