CVE-2026-53164
Last modified
CVE-2026-53164 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: iommu/dma: Do not try to iommu_map a 0 length region in swiotlb iommu_dma_iova_link_swiotlb() processes a mapping that is unaligned in three parts, the head, middle and trailer. If the middle is empty because there are no aligned pages it will call down to iommu_map() with a 0 size which the iommupt implementation will fail as illegal. It then tries to do an error unwind and starts from the wrong spot corrupting the mapping so the eventual destruction triggers a WARN_ON. Check for 0 length and avoid mapping and use offset not 0 as the starting point to unlink. This is frequently triggered by using some kinds of thunderbolt NVMe drives that trigger forced SWIOTLB for unaligned memory. EPSS estimates a 0.17% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: iommu/dma: Do not try to iommu_map a 0 length region in swiotlb iommu_dma_iova_link_swiotlb() processes a mapping that is unaligned in three parts, the head, middle and trailer. If the middle is empty because there are no aligned pages it will call down to iommu_map() with a 0 size which the iommupt implementation will fail as illegal. It then tries to do an error unwind and starts from the wrong spot corrupting the mapping so the eventual destruction triggers a WARN_ON. Check for 0 length and avoid mapping and use offset not 0 as the starting point to unlink. This is frequently triggered by using some kinds of thunderbolt NVMe drives that trigger forced SWIOTLB for unaligned memory. NVMe seems to pass in oddly aligned buffers for the passthrough commands from smartctl that hit this condition.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.16, < 6.18.36 | — |
| Linux | Linux Kernel | >= 6.19, < 7.0.13 | — |
| Linux | Linux Kernel | 7.1 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-53164?
How severe is CVE-2026-53164?
How do I fix CVE-2026-53164?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-53159In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-5316A vulnerability was identified in Nothings stb up to 1.22. T…6.5
- CVE-2026-53160In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53161In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53162In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53163In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53165In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-53166Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2026-53167In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53168In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53169In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-5317A security flaw has been discovered in Nothings stb up to 1.…8.8
Are you affected by CVE-2026-53164?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
