{"api_version":"1","generated_at":"2026-07-14T15:35:27+00:00","cve":"CVE-2026-53164","urls":{"html":"https://cve.report/CVE-2026-53164","api":"https://cve.report/api/cve/CVE-2026-53164.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-53164","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-53164"},"summary":{"title":"iommu/dma: Do not try to iommu_map a 0 length region in swiotlb","description":"In the Linux kernel, the following vulnerability has been resolved:\n\niommu/dma: Do not try to iommu_map a 0 length region in swiotlb\n\niommu_dma_iova_link_swiotlb() processes a mapping that is unaligned in three\nparts, the head, middle and trailer. If the middle is empty because there\nare no aligned pages it will call down to iommu_map() with a 0 size\nwhich the iommupt implementation will fail as illegal.\n\nIt then tries to do an error unwind and starts from the wrong spot\ncorrupting the mapping so the eventual destruction triggers a WARN_ON.\n\nCheck for 0 length and avoid mapping and use offset not 0 as the starting\npoint to unlink.\n\nThis is frequently triggered by using some kinds of thunderbolt NVMe\ndrives that trigger forced SWIOTLB for unaligned memory. NVMe seems to\npass in oddly aligned buffers for the passthrough commands from smartctl\nthat hit this condition.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-06-25 09:16:33","updated_at":"2026-07-07 18:14:53"},"problem_types":["NVD-CWE-noinfo"],"metrics":[{"version":"3.1","source":"nvd@nist.gov","type":"Primary","score":"5.5","severity":"MEDIUM","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","data":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","baseScore":5.5,"baseSeverity":"MEDIUM","attackVector":"LOCAL","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"NONE","integrityImpact":"NONE","availabilityImpact":"HIGH"}}],"references":[{"url":"https://git.kernel.org/stable/c/6ec91df8aff77e2e8fe3179c1f3fc15b43a40ba3","name":"https://git.kernel.org/stable/c/6ec91df8aff77e2e8fe3179c1f3fc15b43a40ba3","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":["Patch"],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/b16f8d40bac9ced838d24c9842707af9ecae92e2","name":"https://git.kernel.org/stable/c/b16f8d40bac9ced838d24c9842707af9ecae92e2","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":["Patch"],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/ab61c990a87d084f5565ee70340543e3a5394697","name":"https://git.kernel.org/stable/c/ab61c990a87d084f5565ee70340543e3a5394697","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":["Patch"],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-53164","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53164","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 433a76207dcf5facc0183acb790f6e8398585258 ab61c990a87d084f5565ee70340543e3a5394697 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 433a76207dcf5facc0183acb790f6e8398585258 b16f8d40bac9ced838d24c9842707af9ecae92e2 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 433a76207dcf5facc0183acb790f6e8398585258 6ec91df8aff77e2e8fe3179c1f3fc15b43a40ba3 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.16","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.16 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.36 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.0.13 7.0.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[{"cve_year":"2026","cve_id":"53164","vulnerable":"1","versionEndIncluding":"","cpe1":"cpe","cpe2":"2.3","cpe3":"o","cpe4":"linux","cpe5":"linux_kernel","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"}],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"53164","cve":"CVE-2026-53164","epss":"0.001660000","percentile":"0.061410000","score_date":"2026-07-04","updated_at":"2026-07-05 00:02:27"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/iommu/dma-iommu.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"ab61c990a87d084f5565ee70340543e3a5394697","status":"affected","version":"433a76207dcf5facc0183acb790f6e8398585258","versionType":"git"},{"lessThan":"b16f8d40bac9ced838d24c9842707af9ecae92e2","status":"affected","version":"433a76207dcf5facc0183acb790f6e8398585258","versionType":"git"},{"lessThan":"6ec91df8aff77e2e8fe3179c1f3fc15b43a40ba3","status":"affected","version":"433a76207dcf5facc0183acb790f6e8398585258","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/iommu/dma-iommu.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.16"},{"lessThan":"6.16","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.36","versionType":"semver"},{"lessThanOrEqual":"7.0.*","status":"unaffected","version":"7.0.13","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.36","versionStartIncluding":"6.16","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.0.13","versionStartIncluding":"6.16","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1","versionStartIncluding":"6.16","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\niommu/dma: Do not try to iommu_map a 0 length region in swiotlb\n\niommu_dma_iova_link_swiotlb() processes a mapping that is unaligned in three\nparts, the head, middle and trailer. If the middle is empty because there\nare no aligned pages it will call down to iommu_map() with a 0 size\nwhich the iommupt implementation will fail as illegal.\n\nIt then tries to do an error unwind and starts from the wrong spot\ncorrupting the mapping so the eventual destruction triggers a WARN_ON.\n\nCheck for 0 length and avoid mapping and use offset not 0 as the starting\npoint to unlink.\n\nThis is frequently triggered by using some kinds of thunderbolt NVMe\ndrives that trigger forced SWIOTLB for unaligned memory. NVMe seems to\npass in oddly aligned buffers for the passthrough commands from smartctl\nthat hit this condition."}],"providerMetadata":{"dateUpdated":"2026-06-25T08:38:44.770Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/ab61c990a87d084f5565ee70340543e3a5394697"},{"url":"https://git.kernel.org/stable/c/b16f8d40bac9ced838d24c9842707af9ecae92e2"},{"url":"https://git.kernel.org/stable/c/6ec91df8aff77e2e8fe3179c1f3fc15b43a40ba3"}],"title":"iommu/dma: Do not try to iommu_map a 0 length region in swiotlb","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-53164","datePublished":"2026-06-25T08:38:44.770Z","dateReserved":"2026-06-09T07:44:35.388Z","dateUpdated":"2026-06-25T08:38:44.770Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-06-25 09:16:33","lastModifiedDate":"2026-07-07 18:14:53","problem_types":["NVD-CWE-noinfo"],"metrics":{"cvssMetricV31":[{"source":"nvd@nist.gov","type":"Primary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","baseScore":5.5,"baseSeverity":"MEDIUM","attackVector":"LOCAL","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"NONE","integrityImpact":"NONE","availabilityImpact":"HIGH"},"exploitabilityScore":1.8,"impactScore":3.6}]},"configurations":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.16","versionEndExcluding":"6.18.36","matchCriteriaId":"C502A34A-34EF-41DB-9280-104B7360171B"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.19","versionEndExcluding":"7.0.13","matchCriteriaId":"6A64BF9F-3BCA-42FD-98CB-8F03474D2B1E"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:7.1:rc1:*:*:*:*:*:*","matchCriteriaId":"B1EF7059-E670-45F4-B422-54C40FA86390"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:7.1:rc2:*:*:*:*:*:*","matchCriteriaId":"0D38F0BF-A728-4133-A358-D44A2F7EE6D6"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:7.1:rc3:*:*:*:*:*:*","matchCriteriaId":"EC732D08-5F7B-46D9-B154-E60C7F4F0A97"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:7.1:rc4:*:*:*:*:*:*","matchCriteriaId":"E5910A9D-F60A-409A-B486-FE66BFEBA9B9"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:7.1:rc5:*:*:*:*:*:*","matchCriteriaId":"81DFF19E-9CF8-49C6-8C36-1E4038622933"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:7.1:rc6:*:*:*:*:*:*","matchCriteriaId":"B0E8FC71-3952-444C-83E9-718DBBBEC615"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:7.1:rc7:*:*:*:*:*:*","matchCriteriaId":"1039E95A-8CC3-4C88-8FF9-5C08EEB861C9"}]}]}]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"53164","Ordinal":"1","Title":"iommu/dma: Do not try to iommu_map a 0 length region in swiotlb","CVE":"CVE-2026-53164","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"53164","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\niommu/dma: Do not try to iommu_map a 0 length region in swiotlb\n\niommu_dma_iova_link_swiotlb() processes a mapping that is unaligned in three\nparts, the head, middle and trailer. If the middle is empty because there\nare no aligned pages it will call down to iommu_map() with a 0 size\nwhich the iommupt implementation will fail as illegal.\n\nIt then tries to do an error unwind and starts from the wrong spot\ncorrupting the mapping so the eventual destruction triggers a WARN_ON.\n\nCheck for 0 length and avoid mapping and use offset not 0 as the starting\npoint to unlink.\n\nThis is frequently triggered by using some kinds of thunderbolt NVMe\ndrives that trigger forced SWIOTLB for unaligned memory. NVMe seems to\npass in oddly aligned buffers for the passthrough commands from smartctl\nthat hit this condition.","Type":"Description","Title":"iommu/dma: Do not try to iommu_map a 0 length region in swiotlb"}]}}}