200 lines
11 KiB
JSON
200 lines
11 KiB
JSON
{
|
|
"dataType": "CVE_RECORD",
|
|
"dataVersion": "5.2",
|
|
"cveMetadata": {
|
|
"cveId": "CVE-2025-22012",
|
|
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
|
"state": "PUBLISHED",
|
|
"assignerShortName": "Linux",
|
|
"dateReserved": "2024-12-29T08:45:45.805Z",
|
|
"datePublished": "2025-04-08T08:18:03.312Z",
|
|
"dateUpdated": "2026-08-05T11:55:58.248Z"
|
|
},
|
|
"containers": {
|
|
"cna": {
|
|
"providerMetadata": {
|
|
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
|
"shortName": "Linux",
|
|
"dateUpdated": "2026-08-05T11:55:58.248Z"
|
|
},
|
|
"descriptions": [
|
|
{
|
|
"lang": "en",
|
|
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nRevert \"arm64: dts: qcom: sdm845: Affirm IDR0.CCTW on apps_smmu\"\n\nThere are reports that the pagetable walker cache coherency is not a\ngiven across the spectrum of SDM845/850 devices, leading to lock-ups\nand resets. It works fine on some devices (like the Dragonboard 845c,\nbut not so much on the Lenovo Yoga C630).\n\nThis unfortunately looks like a fluke in firmware development, where\nlikely somewhere in the vast hypervisor stack, a change to accommodate\nfor this was only introduced after the initial software release (which\noften serves as a baseline for products).\n\nRevert the change to avoid additional guesswork around crashes.\n\nThis reverts commit 6b31a9744b8726c69bb0af290f8475a368a4b805."
|
|
}
|
|
],
|
|
"metrics": [
|
|
{
|
|
"cvssV3_1": {
|
|
"version": "3.1",
|
|
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H",
|
|
"baseScore": 8.8,
|
|
"baseSeverity": "HIGH"
|
|
},
|
|
"scenarios": [
|
|
{
|
|
"lang": "en",
|
|
"value": "AV:L - The flaw is in the local platform description of the SoC's IOMMU, and the stale-pagetable condition is provoked by driving DMA map/unmap churn on locally attached masters (UFS, SD, PCIe, IPA, DSPs) via ordinary syscall-level I/O. There is no remote protocol entry point into the io-pgtable update path.\nAC:L - On an affected SDM845/850 unit the driver omits page-table cache maintenance unconditionally on every single map and unmap, so an attacker needs only to issue I/O to make the walker consume stale entries — no race to win and no uncontrolled precondition. Cache pressure needed to make a specific PTE go stale is itself attacker-influenceable through allocation activity.\nPR:L - Any unprivileged local account can generate the required IOMMU mapping churn through normal file I/O, network traffic, or DSP/crypto offload; no capability, CAP_SYS_ADMIN, or namespace trick is needed. The condition additionally manifests during boot with no authenticated user at all.\nUI:N - The attacker drives DMA activity entirely from its own processes, and the incoherent walker misbehaves as a direct result. No administrator or victim action is required.\nS:C - The SMMU is the authority that confines DMA-capable peripherals to their assigned address space, and translating from stale or garbage page tables lets those peripherals — PCIe endpoints, the SD controller, UFS, IPA, and the cDSP/aDSP firmware — reach physical memory outside their IOMMU domain. This is an IOMMU/DMA containment bypass, and the same flag is what gates VFIO/iommufd device assignment to guests.\nC:H - A master walking stale or uninitialized page-table contents obtains translations to arbitrary physical frames and can read kernel or other-process memory into buffers the attacker can subsequently retrieve. This is an unbounded physical-memory read primitive, not a limited pointer leak.\nI:H - The same broken translations apply to DMA writes: entries the CPU cleared remain live to the walker, so a device keeps writing into pages that were unmapped and reallocated to kernel data or page tables. Directing device DMA at attacker-chosen physical memory is an arbitrary-write primitive leading to privilege escalation.\nA:H - The upstream report is explicit that this causes lock-ups and resets on affected SDM845/850 devices such as the Lenovo Yoga C630, and unresolvable translations raise SMMU global faults that trigger full SoC resets on Qualcomm platforms."
|
|
}
|
|
]
|
|
}
|
|
],
|
|
"affected": [
|
|
{
|
|
"product": "Linux",
|
|
"vendor": "Linux",
|
|
"defaultStatus": "unaffected",
|
|
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
|
|
"programFiles": [
|
|
"arch/arm64/boot/dts/qcom/sdm845.dtsi"
|
|
],
|
|
"versions": [
|
|
{
|
|
"version": "6b31a9744b8726c69bb0af290f8475a368a4b805",
|
|
"lessThan": "9e6e9fc90258a318d30b417bcccda908bb82ee9d",
|
|
"status": "affected",
|
|
"versionType": "git"
|
|
},
|
|
{
|
|
"version": "6b31a9744b8726c69bb0af290f8475a368a4b805",
|
|
"lessThan": "f00db31d235946853fb430de8c6aa1295efc8353",
|
|
"status": "affected",
|
|
"versionType": "git"
|
|
}
|
|
]
|
|
},
|
|
{
|
|
"product": "Linux",
|
|
"vendor": "Linux",
|
|
"defaultStatus": "affected",
|
|
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
|
|
"programFiles": [
|
|
"arch/arm64/boot/dts/qcom/sdm845.dtsi"
|
|
],
|
|
"versions": [
|
|
{
|
|
"version": "6.13",
|
|
"status": "affected"
|
|
},
|
|
{
|
|
"version": "0",
|
|
"lessThan": "6.13",
|
|
"status": "unaffected",
|
|
"versionType": "semver"
|
|
},
|
|
{
|
|
"version": "6.13.9",
|
|
"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.13",
|
|
"versionEndExcluding": "6.13.9"
|
|
},
|
|
{
|
|
"vulnerable": true,
|
|
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
|
|
"versionStartIncluding": "6.13",
|
|
"versionEndExcluding": "6.14"
|
|
}
|
|
]
|
|
}
|
|
]
|
|
}
|
|
],
|
|
"references": [
|
|
{
|
|
"url": "https://git.kernel.org/stable/c/9e6e9fc90258a318d30b417bcccda908bb82ee9d"
|
|
},
|
|
{
|
|
"url": "https://git.kernel.org/stable/c/f00db31d235946853fb430de8c6aa1295efc8353"
|
|
}
|
|
],
|
|
"title": "Revert \"arm64: dts: qcom: sdm845: Affirm IDR0.CCTW on apps_smmu\"",
|
|
"x_generator": {
|
|
"engine": "bippy-1.2.0"
|
|
}
|
|
},
|
|
"adp": [
|
|
{
|
|
"problemTypes": [
|
|
{
|
|
"descriptions": [
|
|
{
|
|
"type": "CWE",
|
|
"cweId": "CWE-667",
|
|
"lang": "en",
|
|
"description": "CWE-667 Improper Locking"
|
|
}
|
|
]
|
|
}
|
|
],
|
|
"metrics": [
|
|
{
|
|
"cvssV3_1": {
|
|
"scope": "UNCHANGED",
|
|
"version": "3.1",
|
|
"baseScore": 5.5,
|
|
"attackVector": "LOCAL",
|
|
"baseSeverity": "MEDIUM",
|
|
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
|
|
"integrityImpact": "NONE",
|
|
"userInteraction": "NONE",
|
|
"attackComplexity": "LOW",
|
|
"availabilityImpact": "HIGH",
|
|
"privilegesRequired": "LOW",
|
|
"confidentialityImpact": "NONE"
|
|
}
|
|
},
|
|
{
|
|
"other": {
|
|
"type": "ssvc",
|
|
"content": {
|
|
"timestamp": "2025-10-01T17:06:54.467971Z",
|
|
"id": "CVE-2025-22012",
|
|
"options": [
|
|
{
|
|
"Exploitation": "none"
|
|
},
|
|
{
|
|
"Automatable": "no"
|
|
},
|
|
{
|
|
"Technical Impact": "partial"
|
|
}
|
|
],
|
|
"role": "CISA Coordinator",
|
|
"version": "2.0.3"
|
|
}
|
|
}
|
|
}
|
|
],
|
|
"title": "CISA ADP Vulnrichment",
|
|
"providerMetadata": {
|
|
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
|
|
"shortName": "CISA-ADP",
|
|
"dateUpdated": "2025-10-01T17:06:57.968Z"
|
|
}
|
|
}
|
|
]
|
|
}
|
|
} |