{"vulnerability": "CVE-2024-42233", "sightings": [{"uuid": "cedf2b63-f314-4645-8f42-a6e688cb30cd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-42233", "type": "seen", "source": "https://t.me/cvedetector/2715", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-42233 - Linux Kernel PTE Unmap Use-After-Free Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-42233 \nPublished : Aug. 7, 2024, 4:15 p.m. | 15\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nfilemap: replace pte_offset_map() with pte_offset_map_nolock()  \n  \nThe vmf->ptl in filemap_fault_recheck_pte_none() is still set from  \nhandle_pte_fault().  But at the same time, we did a pte_unmap(vmf->pte).   \nAfter a pte_unmap(vmf->pte) unmap and rcu_read_unlock(), the page table  \nmay be racily changed and vmf->ptl maybe fails to protect the actual page  \ntable.  Fix this by replacing pte_offset_map() with  \npte_offset_map_nolock().  \n  \nAs David said, the PTL pointer might be stale so if we continue to use  \nit infilemap_fault_recheck_pte_none(), it might trigger UAF.  Also, if  \nthe PTL fails, the issue fixed by commit 58f327f2ce80 (\"filemap: avoid  \nunnecessary major faults in filemap_fault()\") might reappear. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"07 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-07T18:39:32.000000Z"}]}