{"uuid": "0996a743-4f4d-4d1f-b702-4d6f57a4eded", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-39868", "type": "seen", "source": "https://notnow.dev/objects/5fb19aa5-6e98-42ff-9134-703734a521c4", "content": "I\u2019m guessing the vm_shared_region_slide_page_v5 change is one of the kernel memory corruption CVEs (CVE-2026-39868 or CVE-2026-43724, can\u2019t tell)\n\nI don\u2019t see how the vm_map_msync issues can cause kernel memory corruption, so it\u2019s probably not the cve\nvm_shared_region_map_file: an LLM thinks it might lead to read out of bounds and a denial-of-service, but no memory corruption (https://gist.github.com/zhuowei/5a78638228263e02697e43d24c8f63b7); I don\u2019t have enough experience to tell if that\u2019s true\nvm_shared_region_slide_page_v5: seems like you could get some memory corruption - if you manage to map a shared region with a page_starts that points past a page, and have your corruption target on the very next page of physical memory. Can you do that?", "creation_timestamp": "2026-07-03T07:31:41.518355Z"}