{"vulnerability": "CVE-2023-52910", "sightings": [{"uuid": "a19cbbe1-5be2-4fad-b9a1-6c7ad6f902b9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52910", "type": "seen", "source": "https://t.me/cvedetector/3748", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2023-52910 - \"Linux kernel IOMMU iova: Allocation Size Overflow Vulnerability in `__alloc_and_insert_iova_range`\"\", \n  \"Content\": \"CVE ID : CVE-2023-52910 \nPublished : Aug. 21, 2024, 7:15 a.m. | 35\u00a0minutes ago \nDescription : 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 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. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"21 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-21T09:52:13.000000Z"}]}