{"id":"CVE-2023-52910","state":"PUBLISHED","title":"iommu/iova: Fix alloc iova overflows issue","description":"In the Linux kernel, the following vulnerability has been resolved:\n\niommu/iova: Fix alloc iova overflows issue\n\nIn __alloc_and_insert_iova_range, there is an issue that retry_pfn\noverflows. The value of iovad->anchor.pfn_hi is ~0UL, then when\niovad->cached_node is iovad->anchor, curr_iova->pfn_hi + 1 will\noverflow. As a result, if the retry logic is executed, low_pfn is\nupdated to 0, and then new_pfn < low_pfn returns false to make the\nallocation successful.\n\nThis issue occurs in the following two situations:\n1. The first iova size exceeds the domain size. When initializing\niova domain, iovad->cached_node is assigned as iovad->anchor. For\nexample, the iova domain size is 10M, start_pfn is 0x1_F000_0000,\nand the iova size allocated for the first time is 11M. The\nfollowing is the log information, new->pfn_lo is smaller than\niovad->cached_node.\n\nExample log as follows:\n[  223.798112][T1705487] sh: [name:iova&]__alloc_and_insert_iova_range\nstart_pfn:0x1f0000,retry_pfn:0x0,size:0xb00,limit_pfn:0x1f0a00\n[  223.799590][T1705487] sh: [name:iova&]__alloc_and_insert_iova_range\nsuccess start_pfn:0x1f0000,new->pfn_lo:0x1efe00,new->pfn_hi:0x1f08ff\n\n2. The node with the largest iova->pfn_lo value in the iova domain\nis deleted, iovad->cached_node will be updated to iovad->anchor,\nand then the alloc iova size exceeds the maximum iova size that can\nbe allocated in the domain.\n\nAfter judging that retry_pfn is less than limit_pfn, call retry_pfn+1\nto fix the overflow issue.","publishedAt":"2024-08-21T06:10:51.337Z","updatedAt":"2026-08-05T09:11:57.069Z","severity":{"score":8.8,"label":"High","version":"3.1","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","source":"Linux"},"assigner":"Linux","products":["Linux Linux"],"affected":[{"vendor":"Linux","product":"Linux","defaultStatus":"unaffected","versions":[{"version":"4e89dce725213d3d0b0475211b500eda4ef4bf2f","status":"affected","lessThan":"c929a230c84441e400c32e7b7b4ab763711fb63e","versionType":"git"},{"version":"4e89dce725213d3d0b0475211b500eda4ef4bf2f","status":"affected","lessThan":"61cbf790e7329ed78877560be7136f0b911bba7f","versionType":"git"},{"version":"4e89dce725213d3d0b0475211b500eda4ef4bf2f","status":"affected","lessThan":"dcdb3ba7e2a8caae7bfefd603bc22fd0ce9a389c","versionType":"git"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/iommu/iova.c"]},{"vendor":"Linux","product":"Linux","defaultStatus":"affected","versions":[{"version":"5.11","status":"affected"},{"version":"0","status":"unaffected","lessThan":"5.11","versionType":"semver"},{"version":"5.15.89","status":"unaffected","lessThanOrEqual":"5.15.*","versionType":"semver"},{"version":"6.1.7","status":"unaffected","lessThanOrEqual":"6.1.*","versionType":"semver"},{"version":"6.2","status":"unaffected","lessThanOrEqual":"*","versionType":"original_commit_for_fix"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/iommu/iova.c"]}],"references":["https://git.kernel.org/stable/c/c929a230c84441e400c32e7b7b4ab763711fb63e","https://git.kernel.org/stable/c/61cbf790e7329ed78877560be7136f0b911bba7f","https://git.kernel.org/stable/c/dcdb3ba7e2a8caae7bfefd603bc22fd0ce9a389c"],"weaknesses":[],"ingestedAt":"2026-10-29T20:06:33.064Z","source":{"repository":"CVEProject/cvelistV5","path":"cves/2023/52xxx/CVE-2023-52910.json","commit":"556c9d3a8cd17e218bb8e452ba7cd619a384ff47"},"raw":{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2023-52910","state":"PUBLISHED","datePublished":"2024-08-21T06:10:51.337Z","dateUpdated":"2026-08-05T09:11:57.069Z","assignerShortName":"Linux","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","dateReserved":"2024-08-21T06:07:11.015Z"},"containers":{"cna":{"title":"iommu/iova: Fix alloc iova overflows issue","descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\niommu/iova: Fix alloc iova overflows issue\n\nIn __alloc_and_insert_iova_range, there is an issue that retry_pfn\noverflows. The value of iovad->anchor.pfn_hi is ~0UL, then when\niovad->cached_node is iovad->anchor, curr_iova->pfn_hi + 1 will\noverflow. As a result, if the retry logic is executed, low_pfn is\nupdated to 0, and then new_pfn < low_pfn returns false to make the\nallocation successful.\n\nThis issue occurs in the following two situations:\n1. The first iova size exceeds the domain size. When initializing\niova domain, iovad->cached_node is assigned as iovad->anchor. For\nexample, the iova domain size is 10M, start_pfn is 0x1_F000_0000,\nand the iova size allocated for the first time is 11M. The\nfollowing is the log information, new->pfn_lo is smaller than\niovad->cached_node.\n\nExample log as follows:\n[  223.798112][T1705487] sh: [name:iova&]__alloc_and_insert_iova_range\nstart_pfn:0x1f0000,retry_pfn:0x0,size:0xb00,limit_pfn:0x1f0a00\n[  223.799590][T1705487] sh: [name:iova&]__alloc_and_insert_iova_range\nsuccess start_pfn:0x1f0000,new->pfn_lo:0x1efe00,new->pfn_hi:0x1f08ff\n\n2. The node with the largest iova->pfn_lo value in the iova domain\nis deleted, iovad->cached_node will be updated to iovad->anchor,\nand then the alloc iova size exceeds the maximum iova size that can\nbe allocated in the domain.\n\nAfter judging that retry_pfn is less than limit_pfn, call retry_pfn+1\nto fix the overflow issue."}],"affected":[{"vendor":"Linux","product":"Linux","defaultStatus":"unaffected","versions":[{"version":"4e89dce725213d3d0b0475211b500eda4ef4bf2f","status":"affected","lessThan":"c929a230c84441e400c32e7b7b4ab763711fb63e","versionType":"git"},{"version":"4e89dce725213d3d0b0475211b500eda4ef4bf2f","status":"affected","lessThan":"61cbf790e7329ed78877560be7136f0b911bba7f","versionType":"git"},{"version":"4e89dce725213d3d0b0475211b500eda4ef4bf2f","status":"affected","lessThan":"dcdb3ba7e2a8caae7bfefd603bc22fd0ce9a389c","versionType":"git"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/iommu/iova.c"]},{"vendor":"Linux","product":"Linux","defaultStatus":"affected","versions":[{"version":"5.11","status":"affected"},{"version":"0","status":"unaffected","lessThan":"5.11","versionType":"semver"},{"version":"5.15.89","status":"unaffected","lessThanOrEqual":"5.15.*","versionType":"semver"},{"version":"6.1.7","status":"unaffected","lessThanOrEqual":"6.1.*","versionType":"semver"},{"version":"6.2","status":"unaffected","lessThanOrEqual":"*","versionType":"original_commit_for_fix"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/iommu/iova.c"]}],"references":[{"url":"https://git.kernel.org/stable/c/c929a230c84441e400c32e7b7b4ab763711fb63e"},{"url":"https://git.kernel.org/stable/c/61cbf790e7329ed78877560be7136f0b911bba7f"},{"url":"https://git.kernel.org/stable/c/dcdb3ba7e2a8caae7bfefd603bc22fd0ce9a389c"}],"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 bug is in the IOVA allocator used by dma-iommu (and related drivers); it is reached when a local process causes a DMA mapping larger than the IOVA domain via device interfaces such as V4L2/DRM/camera on MediaTek platforms, not via network packet processing.\nAC:L - Triggering is deterministic once an allocation exceeds the domain size while cached_node is the anchor (empty domain or after freeing the top IOVA): the pfn_hi+1 wrap to 0 reliably makes the oversized alloc succeed, and the attacker controls buffer size and alloc/free sequencing.\nPR:L - On the highest-impact deployments (MediaTek Android phones with small per-device IOVA regions), unprivileged apps can request large DMA-mapped media/GPU buffers through standard device nodes without real root or init-namespace capabilities.\nUI:N - The attacking process alone issues the buffer allocations/DMA maps that hit the overflow path; no separate victim action is required.\nS:C - On MediaTek IOMMU, multiple IOVA regions share one page table and rely on software apertures for isolation; allocating below start_pfn installs translations into another device region's IOVA space, breaking the IOMMU/DMA isolation boundary between device groups.\nC:H - Cross-region PTE installation in the shared page table can redirect another device's DMA reads onto attacker-controlled buffers or expose other devices' memory via confused DMA mappings, yielding a high-impact disclosure primitive.\nI:H - The same out-of-aperture mapping can overwrite or collide with another master's IOVA translations in the shared pgtable, so device DMA writes land on the wrong physical pages — a high-integrity memory corruption primitive across the DMA isolation boundary.\nA:H - Conflicting IOVA translations and DMA to addresses outside the intended aperture reliably produce IOMMU faults, WARN_ONs in the page-table code, and kernel oopses/panics."}]}],"providerMetadata":{"shortName":"Linux","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","dateUpdated":"2026-08-05T09:11:57.069Z"},"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.11","versionEndExcluding":"5.15.89"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.11","versionEndExcluding":"6.1.7"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.11","versionEndExcluding":"6.2"}]}]}],"x_generator":{"engine":"bippy-1.2.0"}},"adp":[{"title":"CISA ADP Vulnrichment","metrics":[{"other":{"type":"ssvc","content":{"id":"CVE-2023-52910","role":"CISA Coordinator","options":[{"Exploitation":"none"},{"Automatable":"no"},{"Technical Impact":"partial"}],"version":"2.0.3","timestamp":"2024-09-10T15:34:52.014408Z"}}}],"providerMetadata":{"shortName":"CISA-ADP","orgId":"134c704f-9b21-4f2e-91b3-4a467353bcc0","dateUpdated":"2024-09-12T17:33:03.507Z"}}]}}}