CVE-2026-93137
CVE CVE-2026-93137EUVD EUVD-2026-82245Published 2026-09-17T16:11:38.000ZLast changed 2026-09-18T17:56:08.000ZCVSS 7.8
What the advisory describes
In the Linux kernel, the following vulnerability has been resolved: bpf: Fix use-after-free on mm_struct in bpf_find_vma() bpf_find_vma() reads task->mm and calls mmap_read_trylock(mm) without holding a reference on the mm. On a foreign task, a concurrent exit_mm() can free the mm_struct between the lockless read and the trylock, resulting in a use-after-free. mm_struct is not SLAB_TYPESAFE_BY_RCU. For the current task, task->mm is stable. For a foreign task, pin the mm under task->alloc_lock and release it with mmput_async(), mirroring commit d8e27d2d22b6 ("bpf: fix mm lifecycle in open-coded task_vma iterator"). Use spin_trylock() instead of get_task_mm() so BPF context does not block on alloc_lock. Reject irqs-disabled contexts and !CONFIG_MMU on the foreign-task path because dropping the mm reference is not safe there. Race: CPU0 (BPF program) CPU1 (exiting task) ============================ ========================== bpf_find_vma(foreign_task): mm = task->mm exit_mm(): task->mm = NULL mmput(mm) -> frees mm_struct mmap_read_trylock(mm) // UAF on mm
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux patch: 7.2.6; 7c7e3d31e7856a8260a254f8c71db416f7f9f5a1 <86d54cf069fc5ae2e111c87933bebf6eb527978e; 7c7e3d31e7856a8260a254f8c71db416f7f9f5a1 <db347840d6b6ee9bb9b8e4a985d4b4419f9f3200; patch: 6.6.157; 7c7e3d31e7856a8260a254f8c71db416f7f9f5a1 <c7ad910e987008e125eeff448892e86852173384; patch: 0; patch: 6.18.52; 7c7e3d31e7856a8260a254f8c71db416f7f9f5a1 <2b2a903bee56d312539046d9defa8023eec94760; 7c7e3d31e7856a8260a254f8c71db416f7f9f5a1 <47b079e2117a2ee52e21f8b72935900c702fc0b5; patch: 6.12.110; 5.17; patch: 6.1.188; patch: 7.3-rc1; 7c7e3d31e7856a8260a254f8c71db416f7f9f5a1 <8e1101fc4118019a69c96ced4aec93164f89cbd5
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.